API Keys in latest version (11)

## Feature Request

I would like to continue to pass an API Key from the command-line for local development.

The `--apiKey` parameter is no longer valid on the command-line, but the API keys for my service are all created at runtime for the users that need it. Therefore, it is a bad idea for us to create API Keys in the serverless yaml file. However, locally, I still need to use an API Key and I'd rather it not be a random one started by the server.

This is preventing us from upgrading to the latest version.

Since the documentation still lists `--apiKey` as the correct solution, is there any alternative that still works in version 11?

Start by locating the current command-line option handling for `--apiKey` and the documentation that still lists it as valid. Check how API keys are supplied during local development in version 11 and whether an existing alternative is supported. Done means documenting or implementing a clear way to pass a user-provided key without defining it in serverless configuration.

Written by the indexing model from the issue text.