Update GitHub Action Versions

[wojciechcloudkubed]

Resolves #3847

What is being addressed

Update GitHub Action Versions to the latest ones

Acceptance criteria

• All actions are updated to their latest version

[github-actions]

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 3645dc5.

♻️ This comment has been updated with latest results.

[wojciechcloudkubed]

/test

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/8249878251 (with refid b5620fe6)

(in response to this comment from @wojciechcloudkubed)

[tamirkamara]

@wojciechcloudkubed There's no point in running a test deployment cycle (like with the / test command) when you update the pr_bot or the tre_deploy* workflows as those run from the main branch.

[wojciechcloudkubed]

@wojciechcloudkubed There's no point in running a test deployment cycle (like with the / test command) when you update the pr_bot or the tre_deploy* workflows as those run from the main branch.

What would be the best approach to test it? @tamirkamara

[nasaldrops]

@marrobi I notice some deviation in linting here. Are these changes ok or is there a linter you would ideally like us to use? cc @wojciechcloudkubed @Danny-Cooke-CK

[marrobi]

Github Actions are already checked here -

AzureTRE/.github/workflows/build_validation_develop.yml

Line 87 in ddddbf6

VALIDATE_GITHUB_ACTIONS: true

[marrobi]

@wojciechcloudkubed There's no point in running a test deployment cycle (like with the / test command) when you update the pr_bot or the tre_deploy* workflows as those run from the main branch.

What would be the best approach to test it? @tamirkamara

I typically try to check in my fork of the repo. Unless @tamirkamara has a better way to test.

[marrobi]

LGTM - suggest test it on a fork before merging.

[nasaldrops]

LGTM