FrameMeta: add PreferredVisualizationPluginId field to API

[Umaaz]

What this PR does / why we need it:
This will add the field '' to the FrameMeta type. This is linked to the PR I have open on grafana/grafana grafana/grafana#66982.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[yesoreyeram]

LGTM. @ifrost - does this mean, are we deprecating preferredVisualisationType?

Also can we have set of typed aliases for common/mostly used plugin ids such as timeseries, stat etc to avoid typos in future?

type PluginId string

const (
  PluginIdTimeSeriesPanel PluginId = "timeseries"
  PluginIdStatPanel PluginId = "stat"
)

/// and then use as

PreferredVisualizationPluginID PluginId `json:"preferredVisualisationPluginId,omitempty"`

[ifrost]

does this mean, are we deprecating preferredVisualisationType?

No, preferredVisualisationType is a more generic type, while preferredVisualisationPluginId is used to override the visualization type to a specific plugin. It's marked as alpha, we will see if we need both properties in the future.

Also can we have set of typed aliases for common/mostly used plugin ids such as timeseries, stat etc to avoid typos in furture?

Sounds like a good idea. I'm not sure how to guarantee that such an enum would stay up to date in case something changes or is being added, though. Maybe there should be a schema for it that would generate ts and go types?

[yesoreyeram]

I'm not sure how to guarantee that such an enum would stay up to date in case something changes or is being added, though. Maybe there should be a schema for it that would generate ts and go types?

Usually we don't change plugin ids. So this won't be a problem. Also this accepts string as a fallback. ( for community plugins, string should work as a fallback ). Also this enum approach doesn't guarantee but adding one level of protection and adding convenience.

Just an idea but not necessarily to go with this PR.

[tolzhabayev]

We do not change plugin ids per se but we want to introduce aliases grafana/grafana#69874 and maybe UIDs for plugins internally as heads up to @yesoreyeram and @ifrost (fyi @wbrowne )