Rename extension from 'dynatrace-mcp-server' to 'dynatrace'

[jackwotherspoon]

Gemini CLI team member here 👋

Gemini CLI extensions can be much more than just MCP servers, for that reason we highly recommend removing mcp from their names and instead just use the product (aka dynatrace).

That way users leveraging the extension don't actually need to even know what MCP is 😄

Also the description field in the gemini-extension.json populates the tile card for the extension in our gallery: https://geminicli.com/extensions/

Current

Proposed

I also recommend adding a custom context file (DYNATRACE.md) with best practices for improving Dynatrace workflows and some custom commands to streamline workflows for users. This would take the extension to the next level. 🚀

[dynatrace-cla-bot]

All committers have signed the CLA.

[jackwotherspoon]

@MrManny or @christian-kreuzberger-dtx would one of you mind taking a look 😄

[christian-kreuzberger-dtx]

Hi @jackwotherspoon , thank you for the suggestion!
I'll need to discuss this internally first.

[christian-kreuzberger-dtx]

Hi @jackwotherspoon , we are currently not confident to rename the extension. Dynatrace, as a company, is still looking into distribution strategies of officially maintained components. As this repo contains a community-driven MCP server extension, we would like to reserve the name Dynatrace for any official components that might come later.

Do you see any problems with this approach?