Allow to put env variables inside a folder

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d2vio3fh1kfq9o0

### AWS Region

us-east-1

### Amplify Hosting feature

Environment variables

### Is your feature request related to a problem? Please describe:

is not exactly related to a problem, it is an improvement on how we deploy the env variables

### Describe how you'd like this feature to work

What I want is a way to put a custom env file or variables inside a folder of my deployment, my env variable is not in the root directory of my project, so I can't use the feature of env variables in my project Unfortunately I have to push the commit of my env variables, what I want it is the possibility of uploading an env file in a spesific folder for example in my case I need this "./src/global/env/production.env", so here are my env variables, I found a "solution" [here](https://stackoverflow.com/questions/76709354/how-can-i-access-aws-amplify-environment-variables-from-my-angular-application), but this solution maybe works for one or two variables I have more than 20, the only way I see i can do this is making a bash script and executing the script when I push the repo but this bash script will contain the env variables so I am duplicating myself and pushing the env variables, so it will be nice to have this feature of upload one file or ser the env variables in a specific folder

Start with the Amplify Hosting environment-variable feature and compare the requested path ./src/global/env/production.env with FAQ.md; CONTRIBUTING.md only covers submission guidance. No repository file, test, or implementation entry point is named, so first identify the deployment/configuration component and define how the generated file would be scoped and verified.

Written by the indexing model from the issue text.