[PROPOSAL] : Rename query-insights plugin to opensearch-query-insights

[Panasg]

What/Why

What are you proposing?

I propose to ensure naming consistency across all default plugins bundled with the standard OpenSearch distribution. Currently, most default plugins use the opensearch- prefix, except for the query-insights plugin. To maintain uniformity and improve clarity, I suggest renaming query-insights to opensearch-query-insights or adopting another standardized approach.

What users have asked for this feature?

Developers have noticed the inconsistency in plugin naming conventions, leading to confusion. Standardizing the naming will improve clarity in documentation, plugin management, and integration workflows.

What problems are you trying to solve?

• When managing OpenSearch plugins, a developer wants to easily identify default plugins by their naming convention, so they avoid confusion and ensure consistency.
• When troubleshooting OpenSearch installations, a system administrator wants to quickly distinguish between default and other plugins, so they can efficiently debug and maintain deployments.

What is the developer experience going to be?

Developers will probably need to update references to the query-insights plugin if renamed.

Are there any security considerations?

---

Are there any breaking changes to the API

If the plugin is renamed, it may introduce breaking changes for users who reference it by its existing name in configurations or scripts.

What is the user experience going to be?

---

Are there breaking changes to the User Experience?

Yes, if the query-insights plugin is renamed, users will need to update their references to the plugin in configurations and deployment scripts.

Why should it be built? Any reason not to?

This change aligns with best practices for naming conventions and improves overall usability. The only drawback is the potential migration effort required by existing users.

What will it take to execute?

---

Any remaining open questions?

---

[ansjcy]

@Panasg Thanks for submitting the issue! I think it makes sense to rename the plugin and follow the best format.