ci: coverage report generation should also include testing/src/scenario

[tonyandrewmeyer]

Include testing/src/scenario/ in the coverage analysis.

Additionally, move the (TIOBE required) repositioning of the coverage XML file into the tox command, since it's only used for TIOBE now, and this slightly simplifies the work (since we can use the --data-file and -o options for coverage).

[dimaqq]

I'm a little confused about GHA @vn specifiers.

This source seems to suggest that if it's a tag, then that very tag will be used:
https://github.com/orgs/community/discussions/48058

And TIOBE repo v3 is a tag, while the newest is v3.2.1 (also a tag).

[tonyandrewmeyer]

I'm a little confused about GHA @vn specifiers.

This source seems to suggest that if it's a tag, then that very tag will be used: https://github.com/orgs/community/discussions/48058

And TIOBE repo v3 is a tag, while the newest is v3.2.1 (also a tag).

It looks like TIOBE update the v3 tag to point at the latest v3, so pinning to v3 is the simpler choice because then we don't need to continually update it every time there is a new release.

[tonyandrewmeyer]

This was waiting for a review, so shouldn't really have been merged yet.

[dimaqq]

Oh, it got two reviews, I figured that should be good enough.