Environment Variables revamp

**Community Note**
* Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?

An improved way of handling environment variables. At the moment my in-development application has reached 50/50 environment variables. The page is so damn slow! Editing an environment takes 5-10 seconds just to type a character. And now I'm at a hard limit of 50 I can't do much. I'm going to be revamp my application, but yikes, really?

A [service quota](https://eu-west-2.console.aws.amazon.com/servicequotas/home/services/apprunner/quotas) for environment variables would be nice, but a faster editing page for environment variables would be even nicer.

Also, a way to upload a .env file or CSV would be so much more ideal aswell. A few times i've added ~20 env vars at a time, and then the build fails and I have to re-do it all again! What a pain D:

I use SSM Param store for all of my variables, so a way to add all variables on a path would be nice, e.g. `my_app/staging/`, would be absolutely amazing!

### Summary of ideas:
1. Service Quota application for increase env variable limits
2. CSV/.env file to bulk upload environment variables
3. SSM Param store auto upload by path
4. Page optimisation of `Configuration Tab` of a apprunner Service, as 20+ env vars is INSANELY slow on Chrome.

**Describe alternatives you've considered**
1. None yet, maybe revamp my application
2, 3 and 4. Build a custom wrapper/package that does this automatically with the AWS API

**Attachments**