chore: update github actions major version numbers

[frytg]

Why:

While looking something up about the actions/cache usage I noticed some outdated major version, which would copy an old version from the example code (see https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows#input-parameters-for-the-cache-action). 3 other actions packages seem to outdated too.

What's being changed:

actions/cache is now v4
There are no noteworthy breaking changes in the syntax as per https://github.com/actions/cache/releases

actions/github-script is now v7
also no critical changes https://github.com/actions/github-script/releases

actions/setup-dotnet is now v4
https://github.com/actions/setup-dotnet/releases has no major changes, but helpful due to edgio migrations

actions/stale is now v9
while this seems like a major change from v5, it seems to be mostly behind the scenes and all yaml examples ([1], [2]) are still valid https://github.com/actions/stale/releases

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

👓 Previews for changed content

This comment is 🤖 automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the review server. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-circleci-to-github-actions.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/building-and-testing/building-and-testing-powershell.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/building-and-testing/building-and-testing-ruby.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/deploying/deploying-net-to-azure-app-service.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/deploying/deploying-php-to-azure-app-service.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/deploying/deploying-python-to-azure-app-service.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/writing-workflows/about-workflows.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-jfrog.md	fpt ghec	fpt ghec	from reusable
actions/use-cases-and-examples/project-management/removing-a-label-when-a-card-is-added-to-a-project-board-column.md	ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/building-and-testing/building-and-testing-net.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/building-and-testing/building-and-testing-xamarin-applications.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
actions/use-cases-and-examples/project-management/closing-inactive-issues.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable

---

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
This table is posted from the Content Changes Table Comment workflow.

[nguyenalex836]

@frytg Thanks so much for opening a PR! I'll get this triaged for review ✨

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[nguyenalex836]

@frytg Thank you so much for your patience while our SME team reviewed! They've approved these changes, and I'm in the progress of getting assistance with troubleshooting the failing checks above. Once that is all settled, we'll get this merged 💛

Thank you for this contribution! ✨

[nguyenalex836]

Apologies for the delay! We should have this merged around 4:30pm ET 💛

[nguyenalex836]

Apologies once more - the failed checks are still blocking this, but these should be resolved by Monday, and we'll merge this as soon we're able 💛 thank you again for your patience, and have a great weekend!