Oscap-report commands fails for python3.11 and python3.12

[brandonrace]

Describe the bug
The /usr/bin/oscap-report command references /usr/bin/python3. We symlinked /usr/bin/python3 to either /usr/bin/python3.11 or /usr/bin/python3.12 however it appears there is something else with the package that is relying on python3.9.

To Reproduce
Steps to reproduce the behavior:
On an EC2 instance when installing openscap-report on an instance that does not have python installed on it, it installs python3.9 as a dependency. We want to utilize either python3.11 or python3.12 but it doesn't seem like it is possible since it makes a reference to /usr/bin/python3 in /usr/bin/oscap-report which versions of python greater than 3.9 are not automatically linked to.

Expected behavior
The oscap-report commmand to work on an instance with only python3.11/3.12 on it, and no python3.9.
Screenshots
Attached a screenshot of the error when running oscap-report.

Environment (please complete the following information):

• OS: RedHat Enterprise Linux 9
• Python version: 3.11
• Openscap-report version: 0.2.9-1.el9