Fix spec command for complex data types

[tsokalski]

Modified the spec_command method to use the Flask application's JSON provider instead of the built-in json module when dumping the spec. This provides consistent JSON serialization behavior when using the flask spec command.

Fixes #547.

To ensure access to the .json attribute of the Flask app, I had to bump the minimum Flask version to 2.2.0 (where it was first introduced), which necessitated version bumps of Werkzeug and Flask-HTTPAuth as well. The other versioning changes were auto-generated by pip-compile-multi.

Checklist:

• Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
• Add or update relevant docs, in the docs folder and in code docstring.
• Add an entry in CHANGES.md summarizing the change and linking to the issue.
• Add *Version changed* or *Version added* note in any relevant docs and docstring.
• Run pytest and tox, no tests failed.

[tsokalski]

This change wasn't necessary to get the flask spec command working, but it seemed like it might be helpful, so I included it as well.

[greyli]

We need to support Flask 2.0.x and 2.1.x version, at least before the APIFlask 3.0 version (see also #479). Let's keep the .json attr change to the next major version. For now, we could just import the json module from Flask.

[tsokalski]

We need to support Flask 2.0.x and 2.1.x version, at least before the APIFlask 3.0 version (see also #479). Let's keep the .json attr change to the next major version. For now, we could just import the json module from Flask.

Right, good thinking - I didn't realize the version upgrade was necessary till all the code and tests were done, and it seems overkill just to fix this. Thanks for the suggestion, I've updated the PR.

[greyli]

Merged, thanks! I'll make a new fix release this weekend.