Don't store unmodified state from a saved object in the url

[stacey-gammon]

I was going over this issue #10165, and got to thinking about how we store all this state in the url which creates it's own set of problems.

Currently, as soon as an object is opened, like a dashboard, the url is filled with the saved AppState. If that dashboard is modified, refreshing the page won't pick up those modifications because the url state overrides the saved object state. If we only stored modified state in the url then changes from the saved object would be picked up automatically.

This would result in shorter urls in many situations, like if a user is only interested in viewing a dashboard, not editing it. It would also mean that saved changes would automatically refresh, which is another win.

[stacey-gammon]

related: #10727

[timroes]

On the downside URLs are not directly shareable anymore and undo wouldn't work as easy in the browser anymore. I labelled this with discuss and the new intent-discuss so we can put this into a further meeting discussing if we want to continue with this or not.

[timroes]

I am closing this in favor of #35812 for an aligned discussion around state handling in the URL.