use the new action to create an issue from the output of reportlog

[keewis]

I'm not sure if we actually need the dedicated "report" job, or whether adding an additional step to the main ci job would suffice?

I can see two reasons for a separate job:

1. we get to control the python version independently from the version of the main job
2. we upload the reportlog files as artifacts

I think if we can change the action to abort if it is run on a python version it does not support the first concern would not matter anymore, and for 2 we might just keep the "upload artifact" action (but is it even possible to manually access artifacts? If not we might not even need the upload).

Since I don't think either is a major concern, I went ahead and joined the jobs.

• Closes Convert upstream-dev CI scripts to github Action #6810

[andersy005]

Looks solid to me 👍🏽... Thank you, @keewis!