dateparser.parse() prefers current year also when 'STRICT_PARSING' is True

When I use the dateparser.parse() functionality I expect it to behave the same way for two different input dates that are off by one year. However, based on the current implementation it seems to prefer the current year and detect that in a string. This can be seen in the following comparison:

>>> dateparser.parse('03/06/2020a', settings={'STRICT_PARSING':True})
datetime.datetime(2, 1, 4, 9, 31, 4, 821531)
>>> dateparser.parse('03/06/2022a', settings={'STRICT_PARSING':True})
datetime.datetime(2022, 6, 3, 0, 0)

The same input string, with the only difference of the year 2022a instead of 2020a or 2021a will be parsed correctly if it is the current year. However, this is not deterministic and IMO not expected behavior, as the result will change depending on the current year of the localization.

This applies to the default settings as well as the {'STRICT_PARSING':True} settings.

Could you please advise with which settings I could achieve a deterministic result here? Or ideally improve the implementation here / guide me towards where I could contribute and fix this issue?

Start by reproducing the two dateparser.parse() examples from the issue with and without STRICT_PARSING, then trace the parsing path that handles dates containing a trailing letter. Done should mean equivalent inputs are handled deterministically regardless of the current year, with regression coverage for the reported examples.