Add workflow to tun GET_PYTHON_MODULES against all roles

[spetrosi]

No description provided.

[spetrosi]

@richm please take a look if this workflow needs to do anything special for #40

[spetrosi]

Not tested yet, I just hope that this should work. Once this is managed, we can add comment ``[get_python_modules]` to #40 and it will run on the PR

[spetrosi]

The best way to test this is to fork tft-tests, and in your fork, open a PR in reverse. I.e. do changed on the main branch, then open PR from main to any other branch. This way, the workflow still runs from the main branch, so from the branch where you do changes. You can try cherry-picking commits from #40 and #41 to your fork's branch and open a PR like I described.

[richm]

I don't think we need a separate workflow for this. I have been testing with kernel_settings - linux-system-roles/kernel_settings#226 - I add a comment like this: [citest] GET_PYTHON_MODULES - which will run the ci tests with GET_PYTHON_MODULES=true set. This results in a .packages file for each "regular" log file. https://dl.fedoraproject.org/pub/alt/linuxsystemroles/logs/tf_kernel_settings-226_CentOS-Stream-10-2.17_20240920-001352/artifacts/

I was planning to add a comment to the weekly_ci PRs - [citest] GET_PYTHON_MODULES - at first, just a one time thing

[richm]

The actual workflow change is linux-system-roles/kernel_settings#225
Once I get the bugs worked out, I'll revert this

[spetrosi]

Rich implemented this elsewhere