chore: Updated automation to support PR acceptance tests

[stevehipwell]

Related to #2425

---

Before the change?

• There isn't a way to run acceptance tests from a fork PR
• Linting is showing warning
• Workflows aren't following best practices for security hardening

After the change?

• Acceptance tests can be run from a fork PR
• Linting isn't showing warning
• Workflows have been hardened

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hey Friends, this pull request has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!

[stevehipwell]

/not-stale

[deiga]

This is looking quite good! What would it take to get this finished?

[deiga]

question: Since this produces a coverage.txt would we benefit from uploading the artifact?

[stevehipwell]

Yes I think so and/or integrating with a service to manage coverage.

[stevehipwell]

This is looking quite good! What would it take to get this finished?

@deiga this PR was intended to be a followup to #2476 as it only works if the tests are all actually passing. Before the PR freeze both of these PRs were working correctly and all of the tests were passing, but given the number of PRs merged since then I suspect that there may be quite a lot of changes required. I was planning on looking through the PRs and starting by taking all of the test fixes out into a new smaller and less contentious PR. The main problem here is time, both the lack of it on my side and the passage of it since I did this work that means remembering and validating the changes is going to be tricky.

[stevehipwell]

@deiga I've created #2941 to update the tests. I'll try and have a look at this in isolation but as it requires a number of GitHub repo admin changes I'd need buy in from the GitHub maintainers to make it worth continuing. I think we should take any further discussion back to #2425?

[stevehipwell]

This PR has been replaced by #2946.