[update] Update github action

[LuckyPigeon]

Description

Update GitHub Action to support python3.11.

Fixes #273

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] pytest

Test Configuration:

• OS version: Windows10
• Necessary Libraries (optional):

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules

[LuckyPigeon]

pylint check failed due to python3.11.3 issue, check this for detail.

[rmax]

I'm seeing that others opted to disable pylint meanwhile it gets fixed.

Do you think that's a good option here?

I couldn't figure out if warpt has fixed the issue or not :/

[LuckyPigeon]

wrapt has already fixed the issue, now only use from wrapt import formatargspec instead of from inspect import formatargspec. But seems python team hasn't change the usage.

I'll disable pylint for the meanwhile.

[LuckyPigeon]

And for the pytest failed, seems the new fingerprint implements differently than before, check the official implementation. So, I will rollback to previous request_fingerprint for the meanwhile, then implements our own request_fingerprint in another PR.

[LuckyPigeon]

@rmax I think that's about it. Over all, we stopped pylint for now and do the full checking of python3.11 support, now the rests are setup.py, pip and our next release.