Missing features in content packs for continuously updated content

## What?

The content pack functionality lends itself to be used for continuously updating shipped content. It already provides support for different revisions of the same content pack. This issue is meant to collect talking points for what is missing to utilize this feature in an efficient way to support content which we are shipping with the product that is supposed to be updated constantly in the easiest way (for content producers) possible.

The current problems are:

* Due to content packs being designed to be installed multiple times, they cannot be used to update e.g. a dashboard in-place. The new dashboard will have a different id, breaking all kinds of references (favorites, last opened, recent activity)
* How to deal with local modifications of the content? We either need to prohibit that or be able to track/merge changes.