Add shellscript filenamePatterns for .env.*

[thernstig]

In some cases, projects use .env files such as .env.development or .env.production or similar things.

Adding this to extensions/shellscript/package.json as a filenamePatterns avoids developers having to add specific "files.associations" to their VS Code settings files.

Fixes #173425

[alexr00]

@thernstig can you share several examples of these .env files? I found https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/fixtures/kitchensink/template/.env.development and that looks more like a properties file then a shellscript file.

[thernstig]

@alexr00 An example would be two different deployments like this, where clients have different databases because an application supports multiple:

.env.production_site_1

export MONGODB_ENABLED=true
export POSTGRES_ENABLED=false

.env.production_site_2

export MONGODB_ENABLED=false
export POSTGRES_ENABLED=true

They could use it in the context of https://direnv.net/ (or similar tools) to load it per environment, setting per-environment config according to The Twelve-Factor App (https://12factor.net/config more specifically).

The example from create-react-app are shell files, see https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/fixtures/kitchensink/template/.env (where one can see ${REACT_APP_BASIC}, https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/fixtures/kitchensink/template/.env.development etc.

[alexr00]

Thank you for the details. Just one more question.

[alexr00]

Thank you for the change!