Add validator rule to detect deviation from Grafana plugin tooling

[cursor]

Problem

We're seeing an increase in plugin submissions that deviate significantly from Grafana's standard plugin tooling. Some submissions are missing essential components like the .config folder entirely, indicating they weren't built using create-plugin or our recommended tooling.

With the rise of LLM-generated code, we expect to see more submissions that don't follow our standards.

Proposed Solution

Add a validator rule that checks whether a plugin deviates too much from our standard tooling. This could include checks for:

• Presence of .config folder
• Expected build configuration files from create-plugin
• Standard project structure alignment
• Required tooling artifacts

Expected Behavior

• Plugins missing critical tooling indicators should fail validation with a clear error message
• The error should guide developers to use create-plugin or align with our tooling standards

Context

This will help reduce manual review time for submissions that clearly don't meet our baseline requirements.