Fix the form state cleanup related to standalone mod component migration

[BLoe]

What does this PR do?

• We were accidentally removing all "unsaved" form states because they do not have a corresponding activated mod component in the mod component redux slice, this fixes that problem

For more information on our expectations for the PR process, see the
code review principles doc

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 74.37%. Comparing base (8318d74) to head (57e0aea).
Report is 172 commits behind head on main.

Files	Patch %	Lines
...itor/hooks/useMigrateStandaloneComponentsToMods.ts	0.00%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9002      +/-   ##
==========================================
+ Coverage   74.24%   74.37%   +0.12%     
==========================================
  Files        1332     1353      +21     
  Lines       40817    41898    +1081     
  Branches     7634     7828     +194     
==========================================
+ Hits        30306    31162     +856     
- Misses      10511    10736     +225     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[BLoe]

Note: This whole concept will be going away soon in an upcoming project phase, when we update the page editor mods list UI and remove the ability to create new standalone mod components in the page editor front end.

[github-actions]

Playwright test results

 118 passed
 4 flaky
 6 skipped

Details

 Open report ↗︎
 128 tests across 43 suites
 12 minutes, 34 seconds
 57e0aea
 For more information on how to debug and view this report, see our readme

Flaky tests

chrome › tests/modLifecycle.spec.ts › create, run, package, and update mod
chrome › tests/pageEditor/addStarterBrick.spec.ts › Add starter brick to mod
edge › tests/pageEditor/addStarterBrick.spec.ts › Add starter brick to mod
chrome › tests/runtime/sidebar/sidebarActivation.spec.ts › initiates sidebar mod activation from activate url click

Skipped tests

chrome › tests/regressions/doNotCloseSidebarOnPageEditorSave.spec.ts › #8104: Do not automatically close the sidebar when saving in the Page Editor
edge › tests/regressions/doNotCloseSidebarOnPageEditorSave.spec.ts › #8104: Do not automatically close the sidebar when saving in the Page Editor
chrome › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options
edge › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options
chrome › tests/runtime/insertAtCursor.spec.ts › Insert at Cursor › 8154: can insert at cursor after opening sidebar from selection menu
edge › tests/runtime/insertAtCursor.spec.ts › Insert at Cursor › 8154: can insert at cursor after opening sidebar from selection menu

[grahamlangford]

Approving, but we should include some testing to prevent a regression (Playwright or Jest)

[github-actions]

No loom links were found in the first post. Please add one there if you'd like to it to appear on Slack.

Do not edit this comment manually.