[BUG] CLI does not fail gracefully when invalid option is passed

[Sebastian-Webster]

Please make sure the following are true before submitting this issue:

• The issue occurs in the latest version
• The issue has not been reported yet (You can search here for existing issues)

Describe the bug

When providing an invalid option (such as a valid option name with a typo or something random like --foo bar) the package does not give a graceful error message indicating that the option provided is invalid. Instead it throws an error.

Command Line Invocation

Invoking with any invalid option, such as --foo, --versionn, etc.

Reproducible Code Example

Not Applicable

Expected behavior

A graceful error message should be given (like what happens when running via application code)

Actual behavior

An error is thrown and does not give the user any helpful advice

Screenshots

None

Environment:

• OS and OS version (e.g macOS 15.0.1): macOS 15.2
• JS runtime and runtime version (E.g Node.js 22.9.0): Node.js v23.5.0
• mysql-memory-server version: 1.8.1
• In which environment does this bug occur? (Application Code, CLI, or both): CLI

Additional context

None

Pull Request

• Tick this if you would be willing to create a pull request to fix this issue.