Support later python features such as Python 3.10 feature "Structural Pattern Matching"

[sschulz92]

Describe the bug

If I want to use the match-case pattern, I can see parse error in the output. I could not find any information which Python versions are officially supported by this plugin. The only information I could find is the file "setup.tmpl" with the newest Python version 3.7.

Please use the following screenshot as the easiest way to reproduce it. This is not how I want to use the match-case in production.

To Reproduce
Steps (or project) to reproduce the behavior:

1. Initialise a gauge project: gauge init python
2. Use the following piece of code:

@step("Almost all words have vowels <table>")
def assert_words_vowel_count(table: Table):
    for row in table:
        word = str(row[0])
        match word:
            case "Gauge":
                assert number_of_vowels(word) == 3
            case "Mingle":
                assert number_of_vowels(word) == 2
            case "Snap" | "GoCD":
                assert number_of_vowels(word) == 1
            case "Rhythm":
                assert number_of_vowels(word) == 0
            case _:
                assert False

3. Run the gauge command
4. See error

Logs

Failed to parse c:\xxx\gauge_match_case_example\step_impl\step_impl.py: The only possible keyword before an atomtrailers is 'await', not 'match'

Expected behavior
I can use Python 3.10 features like the Structural Pattern Matching.

Versions:

• Windows 10 Enterprise 21H2
• Python version 3.10.9

Gauge version: 1.5.4
Commit Hash: 30a0c23

Plugins
-------
html-report (4.2.0)
json-report (0.3.7)
python (0.4.1)
screenshot (0.1.0)

[chadlwilson]

The problem is likely that the parsing is based on https://github.com/PyCQA/baron which seems dead, and likely does not support many things introduced in Python 3.8+, simply given its age.

[sriv]

we may need to look at an alternative like rope (https://rope.readthedocs.io/en/latest/library.html)

[chadlwilson]

Related to #233 also.

At some point in #96 redbaron was replaced with parso, and then replaced again with redbaron in #221 with seemingly little discussion. At least parso is still supported, redbaron/baron is definitely dead.

[sriv]

I guess at some point parso didnt do so well with python 3.9 (#220) and hence @bugdiver removed the parso support and made redbaron the default (and redbaron was quite well maintained back then)

We could bring back the option to swap parsers based on the previous commits