Test plan to verify end to end agent tasks to replace release planner

[praveenkuttappan]

This issue highlights the main tasks that will be disabled on release planner to ensure all of these same use cases are supported by agent and release plan dashboard.

Test instance of release plan dashboard: https://releaseplan-dashboard-test.azurewebsites.net/

MUST TO DO AS PREREQUISITE

• Setup the env variable AZSDKTOOLS_AGENT_TESTING to true to ensure release plan is created/updated in test instance only.
• Clone or fetch latest from upstream azure-rest-api-specs before the test.

Spec projects: Any projects with tspconfig.yaml.
Following are the few options.

• specification\containerservice\resource-manager\Microsoft.ContainerService\fleet
• specification\contosowidgetmanager\Contoso.Management
• specification\cognitiveservices\CognitiveServices.Management

High level scenarios to verify that will no longer be available on release planner:

1. Create release plan
2. Generate SDK
3. Link a different API spec to release plan
4. Update SDK details in release plan

Scenarios

1. Create a release plan
Goal: Create all three types of release plans.

• Private preview release plan
  Sample prompt: Create a release plan for TypeSpec project <specification/your-service/Your.Management> and API release type Private Preview

• Public preview release plan
  Sample prompt: Create a release plan for TypeSpec project <specification/your-service/Your.Management> and API release type Private Preview

• GA
  Create a release plan for TypeSpec project <specification/your-service/Your.Management> and API release type GA`

Expectation: It should create a release plan. Agent should not ask for service ID and product Id if it already knows that TypeSpec project from previous release plans.

If a release plan already exists for the product, then it will suggest using the existing one or prompts user to confirm if needs to be force created.

2. Generate SDK
Goal: Generate SDK for all languages
Sample prompt: Generate SDK for all languages for release plan < release plan number>
Expectation: It should call the MCP tool to generate SDK for each language in the release plan.
Out of scope: Any SDK generation issues due to customization needs for the TypeSpec project is outside the scope of this test.

Make sure to update the SDK title manually to include "Test PR: Ignore" or close the PR once it's generated

3. Link a spec PR
Goal: Link a different spec PR to release plan
Sample prompt: Update API spec PR in the release plan or Link a different API spec PR to release plan.

Expectation: API spec PR in the release plan must be updated to new spec PR and this should be reflected when you get release plan details.

4. Update SDK details

• Goal: Update package names in release plan
  Sample prompt: Update SDK details or package names in the release plan.

Expectation: Agent will run MCP tool to parse the TypeSpec config yaml and update package names in release plan based on the emitter configuration in tspconfig.yaml.