Add tool for getting code quality findings

[koesie10]

Summary

This adds a new tool to get a single code quality finding by its finding number. It returns the response that the REST API returns.

Why

See internal linked issue. This will allow Copilot to retrieve and fix Code Quality findings

What changed

• Adds a new get_code_quality_finding tool and runs the various scripts to update the docs/retrieve icon
• Adds a new code_quality toolset that contains the tool

MCP impact

• No tool or API changes
• Tool schema or behavior changed
• New tool added: get_code_quality_finding

Prompts tested (tool changes only)

• See internal linked issue for the full evaluation, these include:
• "How should I resolve code quality finding 314 for monalisa/smile?"
• "What is the title of code quality finding 29 in monalisa/smile?"
• "What file is code quality finding 29 about in monalisa/smile?"
• "Tell me about code quality finding 29 in monalisa/smile"
• "How severe is code quality finding 29 in monalisa/smile?"

Security / limits

• No security or limits impact
• Auth / permissions considered: The REST API is accessible using the repo scope.
• Data exposure, filtering, or token/size limits considered

Tool renaming

• I am renaming tools as part of this PR (e.g. a part of a consolidation effort)
  • I have added the new tool aliases in deprecated_tool_aliases.go
• I am not renaming tools as part of this PR

Note: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.

Lint & tests

• Linted locally with ./script/lint
• Tested locally with ./script/test

Docs

• Not needed
• Updated (README / docs / examples)