Remove redundant prefixes from fields in PanelCfg schema interface

[sdboyer]

This is the current PanelCfg schema interface contract that all PanelCfg composable kinds must follow:

kindsys/schema_interface.cue

Lines 98 to 109 in b1fe864

	interface: {
	// Defines plugin-specific options for a panel that should be persisted. Required,
	// though a panel without any options may specify an empty struct.
	//
	// Currently mapped to #Panel.options within the dashboard schema.
	PanelOptions: {}
	// Plugin-specific custom field properties. Optional.
	//
	// Currently mapped to #Panel.fieldConfig.defaults.custom within the dashboard schema.
	PanelFieldConfig?: {}
	}

Having the Panel prefix is redundant. Options and FieldConfig would be perfectly sufficient.

The change here is simple enough while we're effectively in pre-launch mode:

• All panel implementations in grafana/grafana will need to be updated
• Names of generated types within panel plugins will need to be updated as well
• Grok will need to be regenerated.

Sooner we do this one, the better, because it's a wildly breaking change 😄

[undef1nd]

Requires the following PRs to be merged:

• Grafana kindsys: Adapt to new flattened lineage syntax in Thema grafana#68034
• Kindsys Remove redundant field prefixes from PanelCfg interface #7
• This PR needs to be updated to use kindsys main as a dependency in Grafana kindsys: Adapt to new PanelCfg schema interface grafana#65297

[sdboyer]

Whoops, in skirting around the lineage flattening PR, i had to modify ordering of these merges. grafana is now on an off-main commit for kindsys, and will have to stay there until we fix grafana/grafana#68034