Update docs metadata mutation logic

[danieljurek]

Example success with template project metadata ambiguity: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=976427&view=logs&j=ceb84d66-6af3-5d95-9875-cd812f26b59e&t=3a6002d8-5197-536e-765b-7e51c84fd258&l=144

[check-enforcer-staging]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[danieljurek]

• Releasing the JS template package (with the new changes onboarded) succeeds (this was run against the branch, not part of this PR but illustrative of the changes in this PR working)
• Releasing other packages that don't have the new changes onboarded (also JS in the case of this PR) succeeds (except Python)
  • Python is failing for reasons unrelated to this change. Separate investigation is ongoing
• All CI runs for related PRs have completed successfully

Ready for merge @weshaggard

[ghost]

Hello @azure-sdk!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.