Supporting longer resource suffix names + Supporting substitutions of values from parents

[eladiw]

Resolves #2893

What is being addressed

This PR addresses issue 2893, where the currently selected suffix of resources (4 chars) is not big enough, hence we sometimes get conflicting resource names (and deployments fail).

It achieves the goal by enhancing the already existing properties substitution mechanism so it will be able to fetch properties from the parents as well (for a user resource, it means from the ws and the ws-svc, for a workspace service it means from the workspace).
This mechanism can be used for other purposes in the future...

How is this addressed

• Updated the substitution mechanism to receive 2 more dictionaries of the 2 parents.
• by adding a prefix we can select from which parent we want to fetch the values
• e.g. "{{ parent_workspace.resource.properties.unique_identifier_suffix }}" vs "{{ parent_workspace_service.resource.properties.unique_identifier_suffix }}" vs "{{ resource.properties.unique_identifier_suffix }}" (see screenshot)

• Backwards compatibility: when installing a ws service on a workspace with the 'old'/shorter suffix it will also be with a shorter suffix, same for a user resource on a workspace with the shorter suffix, otherwise things will break
• Backwards compatibility: when upgrading a resource if it had the shorter name it will remain so, otherwise many Azure resources will get recreated and break.
• Updated unittests
• Currently done for the workspace base, guacamole workspace service and a single guacamole user resource templates only.
• Once approved will be applied to the rest

How was this PR tested

• Unittests
  Manually with the following scenarios
• Created a TRE environment without this PR. Created a workspace (4 chars suffix - old one)
  -Registered the new bundles (ws, ws service and user resource)
• created in the workspace a guacamole resource -> created with 4 chars
• created in it a user resource -> created with 4 chars
• Created a new workspace -> created with 6 chars
• created in it a guacamole resource -> created with 6 chars
• same for the user resource
• Verified it works and everything it wired correctly

workspace resource entry:

Guacamole resource entry:

User resource entry:

[github-actions]

Unit Test Results

560 tests   560 ✔️  13s ⏱️
    1 suites      0 💤
    1 files        0 ❌

Results for commit e99dc0e.

♻️ This comment has been updated with latest results.