Airlock UI: support multiple review vms

[jjgriff93]

Resolves #2764

What is being addressed

This PR adds support in the API and UI for multiple reviewers being able to create review VMs for an airlock request. This also adds functionality for re-deploying a review resource if it's in a failed state and automatic clean-up of the previous resource.

How is this addressed

• Changed reviewUserResources from array to dictionary, using the signed-in user's userId as the key to ensure one user resource per user
• Added migration to update from previous format
• Expanded /create-review-resource API to do a check for an existing resource, in which case it checks its health, returns a 409 conflict if healthy, otherwise redeploys and removes the old failed resource
• Also made some general improvements to the airlock experience - allowed actions are now returned with most airlock API calls meaning the user doesn't need to refresh the UI for some options to appear when a request is updated
• Review user resource block shows loading shimmers/spinner instead of defaulting to not created view when looking up an existing resource
• Updated to React 18 and updated dependencies to latest versions
• Update CHANGELOG.md

[github-actions]

Unit Test Results

522 tests   521 ✔️  19s ⏱️
    1 suites      0 💤
    1 files        1 ❌

For more details on these failures, see this check.

Results for commit d37da69.

♻️ This comment has been updated with latest results.

[tanya-borisova]

The API part looks great!
Left some small nits / comments but up to you whether to apply them

[jjgriff93]

/test

[github-actions]

🤖 pr-bot 🤖

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

(in response to this comment from @jjgriff93)

[jjgriff93]

/test-force-approve (no e2e changes wince test pass: https://github.com/microsoft/AzureTRE/actions/runs/3575859656)

[github-actions]

🤖 pr-bot 🤖

✅ Marking tests as complete (for commit d37da69)

(in response to this comment from @jjgriff93)