fix(deps): update astro monorepo (#715)

This PR contains the following updates:

| Package | Change | Age | Confidence |
|---|---|---|---|
|
[@astrojs/sitemap](https://docs.astro.build/en/guides/integrations-guide/sitemap/)
([source](https://redirect.github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap))
| [`3.4.2` ->
`3.5.0`](https://renovatebot.com/diffs/npm/@astrojs%2fsitemap/3.4.2/3.5.0)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@astrojs%2fsitemap/3.5.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@astrojs%2fsitemap/3.4.2/3.5.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [astro](https://astro.build)
([source](https://redirect.github.com/withastro/astro/tree/HEAD/packages/astro))
| [`5.12.9` ->
`5.13.0`](https://renovatebot.com/diffs/npm/astro/5.12.9/5.13.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/astro/5.13.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/astro/5.12.9/5.13.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>withastro/astro (@&#8203;astrojs/sitemap)</summary>

###
[`v3.5.0`](https://redirect.github.com/withastro/astro/blob/HEAD/packages/integrations/sitemap/CHANGELOG.md#350)

##### Minor Changes

-
[#&#8203;13682](https://redirect.github.com/withastro/astro/pull/13682)
[`5824b32`](https://redirect.github.com/withastro/astro/commit/5824b32c5cc5d58c1138e408a05d1be18924c711)
Thanks
[@&#8203;gouravkhunger](https://redirect.github.com/gouravkhunger)! -
Adds a `customSitemaps` option to include extra sitemaps in the
`sitemap-index.xml` file generated by Astro.

This is useful for multi-framework setups on the same domain as your
Astro site (`example.com`), such as a blog at `example.com/blog` whose
sitemap is generated by another framework.

The following example shows configuring your Astro site to include
sitemaps for an externally-generated blog and help center along with the
generated sitemap entries in `sitemap-index.xml`:

  Example:

  ```js
  import { defineConfig } from 'astro/config';
  import sitemap from '@&#8203;astrojs/sitemap';

  export default defineConfig({
    site: 'https://example.com',
    integrations: [
      sitemap({
        customSitemaps: [
          'https://example.com/blog/sitemap.xml',
          'https://example.com/helpcenter/sitemap.xml',
        ],
      }),
    ],
  });
  ```

Learn more in the [`@astrojs/sitemap` configuration
documentation](https://docs.astro.build/en/guides/integrations-guide/sitemap/#configuration).

</details>

<details>
<summary>withastro/astro (astro)</summary>

###
[`v5.13.0`](https://redirect.github.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#5130)

##### Minor Changes

-
[#&#8203;14173](https://redirect.github.com/withastro/astro/pull/14173)
[`39911b8`](https://redirect.github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038)
Thanks
[@&#8203;florian-lefebvre](https://redirect.github.com/florian-lefebvre)!
- Adds an experimental flag `staticImportMetaEnv` to disable the
replacement of `import.meta.env` values with `process.env` calls and
their coercion of environment variable values. This supersedes the
`rawEnvValues` experimental flag, which is now removed.

Astro allows you to configure a [type-safe schema for your environment
variables](https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables),
and converts variables imported via `astro:env` into the expected type.
This is the recommended way to use environment variables in Astro, as it
allows you to easily see and manage whether your variables are public or
secret, available on the client or only on the server at build time, and
the data type of your values.

However, you can still access environment variables through
`process.env` and `import.meta.env` directly when needed. This was the
only way to use environment variables in Astro before `astro:env` was
added in Astro 5.0, and Astro's default handling of `import.meta.env`
includes some logic that was only needed for earlier versions of Astro.

The `experimental.staticImportMetaEnv` flag updates the behavior of
`import.meta.env` to align with [Vite's handling of environment
variables](https://vite.dev/guide/env-and-mode.html#env-variables) and
for better ease of use with Astro's current implementations and
features. **This will become the default behavior in Astro 6.0**, and
this early preview is introduced as an experimental feature.

Currently, non-public `import.meta.env` environment variables are
replaced by a reference to `process.env`. Additionally, Astro may also
convert the value type of your environment variables used through
`import.meta.env`, which can prevent access to some values such as the
strings `"true"` (which is converted to a boolean value), and `"1"`
(which is converted to a number).

The `experimental.staticImportMetaEnv` flag simplifies Astro's default
behavior, making it easier to understand and use. Astro will no longer
replace any `import.meta.env` environment variables with a `process.env`
call, nor will it coerce values.

To enable this feature, add the experimental flag in your Astro config
and remove `rawEnvValues` if it was enabled:

  ```diff
  // astro.config.mjs
  import { defineConfig } from "astro/config";

  export default defineConfig({
  +  experimental: {
  +    staticImportMetaEnv: true
  -    rawEnvValues: false
  +  }
  });
  ```

##### Updating your project

If you were relying on Astro's default coercion, you may need to update
your project code to apply it manually:

```diff
// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;
+ const enabled: boolean = import.meta.env.ENABLED === "true";
```

If you were relying on the transformation into `process.env` calls, you
may need to update your project code to apply it manually:

```diff
// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.DB_PASSWORD;
+ const enabled: boolean = process.env.DB_PASSWORD;
```

You may also need to update types:

```diff
// src/env.d.ts
interface ImportMetaEnv {
  readonly PUBLIC_POKEAPI: string;
-  readonly DB_PASSWORD: string;
-  readonly ENABLED: boolean;
+  readonly ENABLED: string;
}

interface ImportMeta {
  readonly env: ImportMetaEnv;
}

+ namespace NodeJS {
+  interface ProcessEnv {
+    DB_PASSWORD: string;
+  }
+ }
```

See the [experimental static `import.meta.env`
documentation](https://docs.astro.build/en/reference/experimental-flags/static-import-meta-env/)
for more information about this feature. You can learn more about using
environment variables in Astro, including `astro:env`, in the
[environment variables
documentation](https://docs.astro.build/en/guides/environment-variables/).

-
[#&#8203;14122](https://redirect.github.com/withastro/astro/pull/14122)
[`41ed3ac`](https://redirect.github.com/withastro/astro/commit/41ed3ac54adf1025a38031757ee0bfaef8504092)
Thanks [@&#8203;ascorbic](https://redirect.github.com/ascorbic)! - Adds
experimental support for automatic [Chrome DevTools workspace
folders](https://developer.chrome.com/docs/devtools/workspaces)

This feature allows you to edit files directly in the browser and have
those changes reflected in your local file system via a connected
workspace folder. This allows you to apply edits such as CSS tweaks
without leaving your browser tab!

With this feature enabled, the Astro dev server will automatically
configure a Chrome DevTools workspace for your project. Your project
will then appear as a workspace source, ready to connect. Then, changes
that you make in the "Sources" panel are automatically saved to your
project source code.

To enable this feature, add the experimental flag
`chromeDevtoolsWorkspace` to your Astro config:

  ```js
  // astro.config.mjs
  import { defineConfig } from 'astro/config';

  export default defineConfig({
    experimental: {
      chromeDevtoolsWorkspace: true,
    },
  });
  ```

See the [experimental Chrome DevTools workspace feature
documentation](https://docs.astro.build/en/reference/experimental-flags/chrome-devtools-workspace/)
for more information.

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/Tuhura-Tech/wiki).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS43MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNzEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Author: renovate[bot]

package.json

@@ -30,7 +30,7 @@
     "@types/mdast": "4.0.4",
     "@types/node": "22.17.1",
     "@typescript-eslint/parser": "8.39.1",
-    "astro": "5.12.9",
+    "astro": "5.13.0",
     "astro-auto-import": "0.4.4",
     "astro-eslint-parser": "1.2.2",
     "astro-og-canvas": "0.7.0",