Migrate CI to RecordedTests by default

[scbedd]

This issue covers the CI cutover/build definition updates that finalize the CI changes that are related to #1208 .

Where we're at

Here's the situation where we're at once #1208 is complete:

• Any tests that can be recorded are. If a tool is changed, the recorded tests are run as a step in the public build.
• There are exceptions due to non-http usage or not being factored properly for recordings.
  • Speech (websockets use for synthesizers)
  • PostGres (tcp database connection)
  • ConfidentialLedger (presence of a built-in internal identity client creating a new SSL cert for a connection. need to make this available externally somehow and utilize the testproxy adminclient to set the certificate before invoking the tests.)
  • ISV (blocked on inability to record due to resource requirements)
• The mcp - pullrequest - live build still triggers and runs relevant livetests for the change (including a default set of 3)

Where we want to go

Be aware that how we are addressing this has changed pretty substantively. Check edits on this issue for past iterations.

We now have recordings for the majority (and all new) tools in the repo. We need to rely on recordings and see where the gaps are in our existing recorded tests + core validation.

• pull request - live will have it's required check status removed.
• it will still be available to be run manually through /azp run pullrequest - live

The following tools do not support recorded tests at this time:

• Migrate Azure.Mcp.Tools.AzureIsv.LiveTests LiveTests to Recorded Tests #1279
• Migrate Azure.Mcp.Tools.Communication.LiveTests LiveTests to Recorded Tests #1280
• Migrate Azure.Mcp.Tools.ConfidentialLedger.LiveTests LiveTests to Recorded Tests #1281
• Migrate Azure.Mcp.Tools.Cosmos.LiveTests LiveTests to Recorded Tests #1282 (can be solved will be solved)
• Migrate Azure.Mcp.Tools.Speech.LiveTests LiveTests to Recorded Tests #1300

Everyone else is cutover to support recorded command tests.

[anannya03]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @microsoft/azure-mcp.