Avoid using ${{ insert }} duplicate keys with un-rendered yaml validation

[benbp]

The ${{ insert }} template syntax is used twice in one object, which produces valid yaml after render, but is interpreted as invalid yaml before rendering by some of our other validation scripts. This is a quick workaround to change the template syntax to produce the same result, but avoid breaking validation.

From the broken aggregate-reports pipeline

Verifying '/home/ben/sdk/azure-sdk-for-net/eng/pipelines/templates/jobs/archetype-sdk-tests-jobs.yml'
MethodInvocationException: /home/ben/.local/share/powershell/Modules/powershell-yaml/0.4.1/powershell-yaml.psm1:38
Line |
  38 |          $yamlStream.Load([YamlDotNet.Core.IParser] $parser)
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception calling "Load" with "1" argument(s): "(Line: 93, Col: 15, Idx: 2994) - (Line: 93, Col: 28, Idx: 3007): Duplicate key"

InvalidOperation: /home/ben/sdk/azure-sdk-for-net/eng/common/scripts/Verify-Resource-Ref.ps1:12

[weshaggard]

Seems like a reasonable compromise.

[benbp]

/azp run net - aggregate-reports

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[benbp]

/azp run net - keyvault - tests

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[benbp]

Manually queueing the aggregate reports job: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=588540&view=results