Update Instruction tool names to snake case

[jeo02]

Summary

• Changed the tool names to the new snake case naming convention

[Copilot]

Pull Request Overview

This PR updates instruction files to align with new snake_case naming conventions for Azure SDK tools. The changes replace camelCase tool names with their snake_case equivalents across multiple instruction files.

Key Changes

• Updated all tool names from camelCase to snake_case format (e.g., LinkNameSpaceApprovalIssue → azsdk_link_namespace_approval_issue)
• Corrected a filename from .instruction.md to .instructions.md for consistency

Reviewed Changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
verify-namespace-approval.instructions.md	Updated tool name for linking namespace approval issues
typespec-to-sdk.instructions.md	Updated multiple tool names for GitHub operations and SDK generation
sdk-details-in-release-plan.instructions.md	Updated tool name for release plan SDK information updates
create-release-plan.instructions.md	Updated tool names for release plan creation and management
check-package-readiness.instructions.md	Updated tool name for package readiness checks

[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

[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

[weshaggard]

For my context is there a reason for the tool name convention change?

[jeo02]

For my context is there a reason for the tool name convention change?

In this PR #11619 we changed all the names to the tools. Subsequently it changes how the tools are referred to by copilot. To make sure we are referring to the correct tool and not just copilots guess of what tool sounds similar enough we need to change the naming in the instructions as well.

[benbp]

@maririos @jeo02 is it worth thinking about generating these instructions from templates, that way we can inject things that need to reference named properties? Or we can plug it into the tool selection tests once those get spun up.