docs: use ini syntax block highlighting for .env files

docs/1.getting-started/3.configuration.md

@@ -83,7 +83,7 @@ export default defineNuxtConfig({
 })
 ```
 
-```bash [.env]
+```ini [.env]
 # This will override the value of apiSecret
 NUXT_API_SECRET=api_secret_token
 ```

docs/2.guide/2.directory-structure/1.server.md

@@ -328,7 +328,7 @@ export default defineNuxtConfig({
   }
 })
 ```
-```bash [.env]
+```ini [.env]
 NUXT_GITHUB_TOKEN='<my-super-token>'
 ```
 ::

docs/2.guide/2.directory-structure/2.env.md

@@ -15,7 +15,7 @@ Nuxt CLI has built-in [dotenv](https://github.com/motdotla/dotenv) support in de
 
 In addition to any process environment variables, if you have a `.env` file in your project root directory, it will be automatically loaded **at dev, build and generate time**. Any environment variables set there will be accessible within your `nuxt.config` file and modules.
 
-```bash [.env]
+```ini [.env]
 MY_ENV_VARIABLE=hello
 ```
 

docs/2.guide/3.going-further/10.runtime-config.md

@@ -67,7 +67,7 @@ Watch a video from Alexander Lichter showcasing the top mistake developers make
 
 #### Example
 
-```sh [.env]
+```ini [.env]
 NUXT_API_SECRET=api_secret_token
 NUXT_PUBLIC_API_BASE=https://nuxtjs.org
 ```

docs/2.guide/4.recipes/4.sessions-and-authentication.md

@@ -29,7 +29,7 @@ As `nuxt-auth-utils` uses sealed cookies to store session data, session cookies
 If not set, this environment variable will be added to your `.env` automatically when running in development mode.
 ::
 
-```dotenv [.env]
+```ini [.env]
 NUXT_SESSION_PASSWORD=a-random-password-with-at-least-32-characters
 ```
 

docs/3.api/2.composables/use-runtime-config.md

@@ -82,7 +82,7 @@ It is possible to update runtime config values using a matching environment vari
 
 We can set the environment variables inside the `.env` file to make them accessible during **development** and **build/generate**.
 
-``` [.env]
+```ini [.env]
 NUXT_PUBLIC_API_BASE = "https://api.localhost:5555"
 NUXT_API_SECRET = "123"
 ```