Add AllParametersOption as safer alternative to AllParametersOptional

Using AllParametersOptional is more dangerous than it needs to be. Since it makes all parameters optional, you get no compile-time check when you add new parameters to your SQL and forget to add them to Execute/AsyncExecute.

A safer alternative would be to make the parameters option-wrapped instead of implementing them as optional parameters. That way, all parameters would still be mandatory, and you'll get a compiler error if you add new params to your SQL without adding them to Execute/AsyncExecute.

I therefore suggest adding a new option AllParameterOption (in addition to the existing AllParametersOptional), so that users can choose a safer alternative if they want.

(Feel free to choose a better name for the static parameter, of course.)

Start by tracing the existing AllParametersOptional option and its Execute and AsyncExecute entry points. Determine how parameter generation and SQL validation are implemented, then define the new option so parameters are option-wrapped while remaining mandatory. Done means the safer alternative is available alongside AllParametersOptional and enforces missing parameters at compile time.