Chore: Properly manage @grafana package dependency updates

[ashharrison90]

Scenes is now a key part of the grafana core package. But the version of @grafana packages being used in scenes is often 2 or 3 minor versions behind what is currently released. That means if you want to use a newly released feature in one of these grafana packages, you have to also handle upgrading to the latest versions of the packages, including type/test fixes that you don't have any context on.

Upgrade PRs should be raised as soon as new @grafana packages are released. This has 2 benefits:

• Reduces the scope of the changes in each PR
• Keeps context fresh

Suggestions:

• use renovate/dependabot to automatically raise a PR when new versions of @grafana packages are released

[torkelo]

@ashharrison90

Upgrade PRs should be raised as soon as new @grafana packages are released. This has 2 benefits:

The only caveat is that scenes is heavily used in plugins that need to support a range of Grafana versions, how tight that range is (1 or 2 minor versions or more) can be debated :)