[FLOSS T1] Change checking of stale issues/PRs to GitHub action

[0x6178656c]

As discussed in #4476 there is an additional step required when removing the old configuration. There @stefnotch did the research on how to carry out the swtich from probot/stale to the GitHub action.

One notable difference to the previous setup is that the check would now only run daily. (It is straightforward to change this by modifying the cron job configuration.)

Afaict, the cron job would run on a runner from GitHub.

Closes #4476

Basics

• Short descriptions of your changes are in the release notes
  (added as entry in doc/news/_preparation_next_release.md which
  contains _(my name)_)
  Please always add something to the release notes.
• Details of what you changed are in commit messages
  (first line should have module: short statement syntax)
• References to issues, e.g. close #X, are in the commit messages.
• The buildservers are happy. If not, fix in this order:
  • add a line in doc/news/_preparation_next_release.md
  • reformat the code with scripts/dev/reformat-all
  • make all unit tests pass
  • fix all memleaks
• The PR is rebased with current master.

Checklist

• I added unit tests for my code
• I fully described what my PR does in the documentation
  (not in the PR description)
• I fixed all affected documentation (see Documentation Guidelines)
• I fixed all affected decisions (see Decision Process)
• I added code comments, logging, and assertions as appropriate (see Coding Guidelines)
• I updated all meta data (e.g. README.md of plugins and METADATA.ini)
• I mentioned every code not directly written by me in reuse syntax

Review

• Documentation is introductory, concise, good to read and describes everything what the PR does
• Examples are well chosen and understandable
• Code is conforming to our Coding Guidelines
• APIs are conforming to our Design Guidelines
• Code is consistent to our Design Decisions

Labels

• Add the "work in progress" label if you do not want the PR to be reviewed yet.
• Add the "ready to merge" label if the basics are fulfilled and no further pushes are planned by you.

[flo91]

@markus2330 Are you ok with that?

One notable difference to the previous setup is that the check would now only run daily.

If so, then please do the switch as you announced in #4476 (comment)

[markus2330]

LGTM, let us see if it works.

[markus2330]

Which timezone is this?

[0x6178656c]

I fear this is undefined when using GitHub runners.

There is an issue where others have requested the possibility of setting a timezone: actions/runner#1423

If this is important, I could do further research.

[markus2330]

No, not important.

[markus2330]

Any specific reason why you didn't use the latest version (v6.0.1)?

[0x6178656c]

No reason. I adopted the code from https://docs.github.com/en/actions/managing-issues-and-pull-requests/closing-inactive-issues.