feature request: Consider generating command line options

Hey there, I've written a rust and nix library for running azurite without docker. As of right now, it's all hand written and validated, and I'm matching the semver to azurite releases. It would be great if instead of having to manually update the interface as it changes over time, to instead use some kind of spec file to generate the rust and nix interface so it can change automatically as new releases of azurite are made.

This could also have the nice side effect of enabling other languages to do the same, and could prevent the readme or other docs from going out of sync with the interface.

You can find the crate here:
- https://github.com/eureka-cpu/azurite-node-bindings
- https://crates.io/crates/azurite-node-bindings

This is particularly useful for serial unit tests, or perhaps in an environment where docker does not offer a practical advantage. The nix bindings are also quite nice, since it allows you have separation of concerns in VM tests, mimicking a real provider node.

The issue names no Azurite files, tests, or entry points; start by reviewing the command-line option surface and the linked azurite-node-bindings crate. Clarify the proposed spec format, generation targets, and release workflow, then define done as generated interfaces and related documentation staying synchronized with Azurite releases.

Written by the indexing model from the issue text.