adapt packages to check for modifications

[mcalmer]

What does this PR change?

The list of packages to check for compliance was wrong.

• python311-azure-mgmt-billing was removed as it is not on the image anymore
• python-instance-billing-flavor-check was added as it tells us if we are PAYG or not

GUI diff

No difference.

• DONE

Documentation

• No documentation needed: only internal and user invisible changes

• DONE

Test coverage

• No tests: already covered

• DONE

Links

Issue(s):

• DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

• No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

• Re-run test "changelog_test"
• Re-run test "backend_unittests_pgsql"
• Re-run test "java_pgsql_tests"
• Re-run test "schema_migration_test_pgsql"
• Re-run test "susemanager_unittests"
• Re-run test "javascript_lint"
• Re-run test "spacecmd_unittests"

Before you merge

Check How to branch and merge properly!

[agraul]

Personally I would put all packages to check in a list and do

>>> packages_modified = any(has_package_modifications(pkg) for pkg in ["python-instance-billing-flavor-check", "csp-billing-adapter-service", ...])
>>> packages_modified
True

[mcalmer]

@admd @deneb-alpha I added this to the resubmission candidates.