Review skill organization: break out Docs & Metadata Updates into a Prepare for Release skill

## Description

Review the current skill setup for the AzSDK Tools agent. Specifically, evaluate whether the **Docs & Metadata Updates** section currently in the **Generate SDK Locally** skill should be extracted and placed into a separate **Prepare for Release** skill.

The Generate SDK Locally skill may be doing too much by bundling doc/metadata update steps alongside SDK generation. A dedicated Prepare for Release skill would better scope the release-readiness steps (docs, metadata, changelog updates) as a distinct workflow.

## Tasks

- Review the current Generate SDK Locally skill and identify which steps relate to docs/metadata updates
- Determine if those steps are better suited for a standalone Prepare for Release skill
- If yes, draft the new skill and update the existing one
- Ensure no gaps in coverage between the two skills

## Original Context

Ronnie's request: *"Look at the skill setup for the AzSDK Tools agent and see if any should be broken up. Specifically the Docs & Metadata Updates — should those not be in the Generate SDK Locally skill and instead be placed in a Prepare for Release skill?"*

Start by locating the AzSDK Tools agent's skill definitions and reading the Generate SDK Locally skill, especially its Docs & Metadata Updates section. Map the documentation, metadata, and changelog steps to the proposed workflows, then compare both skill scopes for coverage. Done means the skills have a clear separation with no missing release steps.

Written by the indexing model from the issue text.