Add complete support for parameter based configuration

## 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

Am requesting that the [`eb cli`](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3.html) support complete configuration through command line arguments.

For instance, I'd like to be able to run the eb cli command as follows:

```shell
eb deploy --application-name myapp --environment dev
```

### Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

I am trying to solve two problems:

- When running the `eb deploy` command (or other commands) in CI/CD (or on any system where we wish to run an `eb` command without having a `.elasticbeanstalk/config.yml` we need to run `eb init` _or_ create a file named `.elasticbeanstalk/config.yml` prior to running the `eb` tool

- Ensuring a consistent user experience across all AWS provided tooling - I believe most other AWS CLI tools support nearly complete configuration via command line arguments

### Are you currently working around this issue?

Currently we either check-in or create an EB file. Example below:

```yaml
cat > .elasticbeanstalk/config.yml <

Start with the eb deploy and eb init command entry points and trace how .elasticbeanstalk/config.yml supplies application_name and environment. Compare the requested --application-name and --environment invocation with the current CLI behavior. Done means eb deploy can receive those values from command-line arguments without requiring that configuration file.

Written by the indexing model from the issue text.