Description of changes

This PR improves the work started on #2466 and gets inspiration from @AhmadYasser1 CI improvements on #2286 to:

• Ensure all GitHub actions jobs used to verify if other jobs were completed, should always run even if the needed job was skipped
  • Without this change, PRs would be stuck, waiting for the required "Verify ..." job to complete, but as it would only run in case the needed jobs would match "success() || failure()" they would never run when needed job was intentionally skipped
• Improve output messages to separate failed/cancelled jobs from the ones completed or skipped
• Bump node versions to 24 and "setup-node" action to v6, so we can ensure all actions use latest npm versions and prevents incosistency in diffs when "package-lock.json" is auto updated using different "npm" versions, which can cause addition or removal of the line "peer: true". See Document the meaing of peer in the package-lock.json documentation. npm/documentation#1773 and [BUG] npm i after dependabot bumps results in "peer": true added to multiple pkgs npm/cli#8690 (comment) and fix: dep flag calculation npm/cli#8645

GitHub issues resolved by this PR

• N/A

Quality Assurance

• Once the changes in this PR are merged and deployed, success criteria is: all verification jobs will run in all PRs, even when needed jobs were intentionally skipped

More info

Before

Diffs in package-lock.json due to different actions using different npm versions

GitHub actions getting stuck

Without this change, PRs would get stuck with required jobs not being started, and remaining in the "Expected" state. Example: