Dashboard: old panel still present after it was replaced with the new one

[dmlemeshko]

Kibana version: master

Elasticsearch version:

Server OS version: Linux (Jenkins CI workers)

Browser version: Chrome 79

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): build on CI

Describe the bug: Dashboard: old panel still present after it was replaced with the new one

Steps to reproduce:
So far it is daily spotted on our CI: 1 failure on master per day starting Jan 21. Cannot reproduce locally

1. Create a new dashboard, add 2 panels
2. Click panel options button, click Replace panel
3. Select one panel in the list
4. Check the number of panels
   Result: 3 panels are present, replaced one is is still there

Expected behavior: old panel is not present

Screenshots (if relevant):

Errors in browser console (if relevant):

http://localhost:6141/bundles/commons.bundle.js 63187:18 "Detected an unhandled Promise rejection.
TypeError: Cannot assign to read only property 'w' of object '#\u003CObject>'"
http://localhost:6141/bundles/plugin/dashboard_embeddable_container.bundle.js 3181:50 Uncaught TypeError: Cannot assign to read only property 'w' of object '#<Object>'

Provide logs and/or server output (if relevant):

Any additional context:

FAILURE test/functional/apps/dashboard/panel_controls·js dashboard app using legacy data dashboard panel controls visualization object replace flyout replaces old panel with selected panel

Error: expected 3 to equal 2
    at Assertion.assert (packages/kbn-expect/expect.js:100:11)
    at Assertion.be.Assertion.equal (packages/kbn-expect/expect.js:227:8)
    at Assertion.be (packages/kbn-expect/expect.js:69:22)
    at Context.it (test/functional/apps/dashboard/panel_controls.js:76:39)
    at process._tickCallback (internal/process/next_tick.js:68:7)

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[flash1293]

ping @Dosant was this perhaps caused by the app state migration?

[Dosant]

This regressed in #54105 and should be implicitly fixed in #55158.

Unskipping the test in #57093

Just for info:

Cannot reproduce locally

When it was reproducable, I was able to reproduce locally, by forcing state to come from URL. e.g

1. Create a new dashboard, add 2 panels
2. Change position of one of the panels
3. Undo it by browser's back button
4. Click panel options button, click Replace panel
5. Select one panel in the list
6. Check the number of panels
7. Result: 3 panels are present, replaced one is is still there

And that error is in console