Update motdotla/dotenv-expand dep to ^11.0.0

[HugoImaios]

Describe the bug

hey 👋
Current version of motdotla/dotenv-expand (10.0.0 patched by Vite team) contains a bug reported here : #13399 is Vite's issues, and here in dotenv's issues : motdotla/dotenv-expand#98.
It has been adressed upstream in dotenv repo as of v11 🎉, so this new issue here is about upgrading the dep (as the other issue was locked)

Reproduction

https://stackblitz.com/edit/vitejs-vite-brtwpg?file=.env

Steps to reproduce

(using the same repro as the original closed bug)

System Info

System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
    Memory: 29.10 GB / 31.31 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.19 - /mnt/d/programas/nodejs/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  npmPackages:
    vitest: ^0.31.2 => 0.31.2

Used Package Manager

npm

Logs

$ vite

VITE v4.3.9 ready in 826 ms

➜ Local: http://localhost:5173/
➜ Network: use --host to expose
➜ press h to show help
9:54:42 AM [vite] .env changed, restarting server...
9:54:42 AM [vite] server restarted.
9:54:49 AM [vite] .env changed, restarting server...
9:54:49 AM [vite] Maximum call stack size exceeded
9:54:49 AM [vite] server restart failed

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-brtwpg (Open reproduction)