Please introduce startup option to create containers up front, or to create containers automatically

Please introduce startup option to create containers up front, or to create containers automatically. This will be useful in the scenarios where the production infrastructure takes care of container creation.

Without this feature, it is harder to follow these recommendations:

- Let the infrastructure take care of container creation. For apps deployed with Azure DevOps pipelines, this means letting the pipeline take care of container creation.
- [Use a singleton client for all container access](https://learn.microsoft.com/en-us/azure/azure-functions/manage-connections?tabs=csharp#static-clients).

Setting up this singleton is usually done in `Startup.cs` as part of dependency container configuration. This part of the application is not async, and should be non-blocking.

There is no pipelines involved during development, and Azurite doesn't offer a feature to create containers at startup.

Our options are to either create the containers manually, which is a bottleneck during development testing; or to create mitigation code which complicates otherwise simple code.

It would have been nice to start azurite with an argument like `--containers "a, b, c"` to create three containers in this case, or `--auto-create-container=true`

### Which service(blob, file, queue, table) does this issue concern?

blob

### Which version of the Azurite was used?

3.23.0

### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

npm

### What's the Node.js version?

v18.12.1

### What problem was encountered?

Not able to preconfigure azurite with known containers.

### Steps to reproduce the issue?

### Have you found a mitigation/solution?

Write wrapping code around the container client which test for `"UseDevelopmentStorage=true"` at runtime, then create the container.