--env-file does not support inner quotes (does not behave like dotenv)

### Version v20.16.0 ### Platform ```text Darwin <redacted> 23.5.0 Darwin Kernel Version 23.5.0: Wed May 1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020 arm64 ``` ### Subsystem _No response_ ### What steps will reproduce the bug? inspired by this comment: https://github.com/nodejs/node/pull/50814#issuecomment-1817949911 1. create an `.env` file: ```env INNER_QUOTES="1: foo'bar"baz`qux" INNER_QUOTES_WITH_NEWLINE="2: foo bar\ni am "on" newline, 'yo'" ``` 2. test with dotenv: ```js // envtest-dotenv.js require("dotenv").config(); console.log(process.env.INNER_QUOTES); console.log(process.env.INNER_QUOTES_WITH_NEWLINE); ``` `$ node envtest-dotenv.js` 3. test with `--env-file` ```js // envtest.js console.log(process.envconsole.log(process.env.INNER_QUOTES); console.log(process.env.INNER_QUOTES_WITH_NEWLINE); ``` `$ node --env-file=.env envtest.js` ### How often does it reproduce? Is there a required condition? always ### What is the expected behavior? Why is that the expected behavior? outputs should be the same. ```console // dotenv output: 1: foo'bar"baz`qux 2: foo bar i am "on" newline, 'yo' ``` ### What do you see instead? output are different, node native terminates at the first occurrence of the double quote: ```console // --env-file output 1: foo'bar 2: foo bar i am ``` compare that to dotenv: ```console 1: foo'bar"baz`qux 2: foo bar i am "on" newline, 'yo' ``` ### Additional information - this makes it impossible to have env-variables that contain all three quotes (", ' and `) and newlines. - There is no alternative to inner quotes, because escaping quotes have been rejected https://github.com/nodejs/node/pull/50814 - It's very problematic in many cases since depending on the quotes you are using, you need to use different outer quotes - i noticed that because i am writing some tooling that creates those .env files based on some other configuration. I just used double quotes as outer quotes and …