Register TRE bundle workflow

[guybartal]

What is being addressed

This workflow allows TRE Admins to publish and register a specific TRE bundle.

main changes

1. Adding a new Register TRE Bundle workflow with the following inputs:

• Bundle type (workspace, workspace-service, shared-service or user resource
• Bundle name
• Workspace service to register a user resource inside (required only if bundle-type == user-resource)

2. Support for multiple command lines inside devcontainer action for readability and maintainability.

[github-actions]

Unit Test Results

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

Results for commit 4f3c89f.

♻️ This comment has been updated with latest results.

[marrobi]

@guybartal would this be better in the AzureTRE-Deployment repository?

[tim-p-allen]

I would also change it to "Register Bundle" as that's the command its doing

[tim-p-allen]

I think it should probably run a publish before it runs a register too

[tim-p-allen]

@guybartal would this be better in the AzureTRE-Deployment repository?

agree with @marrobi

[guybartal]

@guybartal would this be better in the AzureTRE-Deployment repository?

agree with @marrobi

@tamirkamara WDYT?

[marrobi]

@guybartal would this be better in the AzureTRE-Deployment repository?

agree with @marrobi

@tamirkamara WDYT?

So my reasoning for having it in the deployment repo is:

1. It's unlikely to be run in this repo.
2. Avoids making PRs in this repo, and then having to wait for a release to update the other repo, when an just do it direct in the deployment repo.