[GITHUB] Update Github Actions for Node 16 deprecation preparation

[maj113]

Purpose

Github will start to show deprecation warnings for all Node JS 16 based Github Actions:

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

Proposed changes

• Update Checkout to V4; No major changes, Node version bumped
• Update Labeler to V4 and remove the now optional repo-token argument, supersedes [GITHUB] Update Labeler action to v4 #5753 (Note that this action is still Node16 based)
• Update stale action to V8, it has some breaking changes but none seem to be related to our configuration, remove useless issue permission since we don't have issues enabled (Note that it is still node 16 based Stale V9 is Node20 based)

BLOCKERS

• Actions that need to be updated to NodeJS 20

  • ilammy/msvc-dev-cmd (Update NodeJS to v20 ilammy/msvc-dev-cmd#72)
  • actions/upload-artifact (feat: bump to use node20 runtime, actions/checkout to v4 actions/upload-artifact#434)
  • actions/cache (feat: bump actions/checkout to v4 actions/cache#1231)
  • actions/stale (Update default runtime to node 20 actions/stale#1098)
  • actions/labeler ([Beta] Update Node.js runtime and dependencies actions/labeler#699) will be done in different PR

[SergeGautherie]

  * [ ]  actions/upload-artifact (feat: bump to use node20 runtime, actions/checkout to v4)

See
https://github.blog/changelog/2023-12-14-github-actions-artifacts-v4-is-now-generally-available/

[SergeGautherie]

Labeler and Stale seem ready to be updated too.
Note: I would suggest to do these two on a separate PR(s).

[maj113]

I'll get onto this tomorrow, was waiting for the msvc action to get updated

[maj113]

Labeler and Stale seem ready to be updated too. Note: I would suggest to do these two on a separate PR(s).

I'll keep stale here since it requires no significant changes but labeler action needs a config change so I'll split off that one or leave it to #6326, also looks like cache hasn't been updated yet, should I wait or can I update that one separately at a later date?

[SergeGautherie]

can I update that one separately at a later date?

Yes.

[maj113]

This is ready for review/merge, i'll update cache in a different PR since its taking a while for that to get updated

[maj113]

@binarymaster So..... do i close this?

[binarymaster]

Just resolve conflicts (UPD: done).