Blacklist broken mysql-connector-python v9.7.0

[bmos]

They didn't publish this version correctly, so it's only compatible with some versions of python. It also seems to only contain documentation updates, so it's very weird they pushed it as a minor version change.

What is this change?

• Fix CI + installing from main by blacklisting broken dependency

Considerations for discussion

• Here is what changed between v9.6 and v9.7.
• Here are the files they published to pypi for 9.7.0. You'll see it only supports 3.10 and 3.11.
• Here are the files they published to pypi for 9.6.0. You'll see there are many more files.

How to test the changes (if needed)

• CI tests are adequate

Breaking Changes

Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.

Does this PR introduce breaking changes?

• label: Breaking change — This PR introduces one or more breaking changes.
• label: Non-breaking change — This PR does not introduce one or more breaking changes.

Details (if needed)

• (List out any changes to the API that may cause breaks for developer implementation.)

[bmos]

@shaunagm FTFY :) Unfortunately this is the downside of having such permissive dependency version requirements.

I think #1833 will help avoid this in the future, but the idea of including a lockfile and how we should manage that would benefit from discussion.

[ghost]

Coverage report

This PR does not seem to contain any modification to coverable code.