Tighten requirements, support Flask 2.3.x, track Fixture callbacks

[crscheid]

This pull request addresses issue #49:

• Locks down the requirements to major versions via requirements.txt
• Supports named Blueprints with Flask 2.3
• Increments version 2.0.0 to 2.0.1

[crscheid]

Not sure why scrutinzer cannot find pyftdi 0.55.0 or pyftdi 0.54.0. Successfully tested on MacOS arm64 and Raspberry Pi platforms.

[MattIPv4]

Not sure why scrutinzer cannot find pyftdi 0.55.0 or pyftdi 0.54.0. Successfully tested on MacOS arm64 and Raspberry Pi platforms.

It looks like scrutinzer is running Python 3.6, and 0.54.0 is set to Python 3.7+?

[crscheid]

I didn't realize that the pull request would update from my master after I committed the other changes for callbacks as I meant to do these two sets of changes separately.

That said, I will clean this up in my master branch of my fork and send a note when its done.

[crscheid]

Not sure why scrutinzer cannot find pyftdi 0.55.0 or pyftdi 0.54.0. Successfully tested on MacOS arm64 and Raspberry Pi platforms.

It looks like scrutinzer is running Python 3.6, and 0.54.0 is set to Python 3.7+?

LMK if you plan to update to 3.7+ if not, I'll downgrade pyftdi to support Python 3.6+.

[MattIPv4]

3.6 has been EOL for a while now, so I'd be fine with bumping to 3.7 as part of this :)

[crscheid]

Happy Monday: changes to this PR from my master branch

• Updated setup to require Python >= 3.7 (scrutinizer config for this project might still require an update)
• Bumped version to 2.1.0 due to feature addition of clear_callbacks within FixtureHelper
• Modified internal tracking variable for fixtures to __callbacks as suggested
• Removed remove_local_callbacks from clear_effects. (Since clear_callbacks is in FixtureHelper, no need to have another function at the Fixture level since its already accessible.)

[crscheid]

• Updated Python requirement to >=3.8
• Set Flask requirement at >=2.3

[crscheid]

All good, cheers!