#9092: slice 2.3 support deleting user deployment in extension console

[fungairino]

What does this PR do?

• Closes Slice 2.3 Support deleting user deployment in extension console #9092

Demo

• https://www.loom.com/share/b1ed5e182fd843e8b5d9d8808fa603b5

Future Work

• Handle updating/reactivating to a new version properly (shown in the loom, a work-around is to reactivate turning sync off, and then turning it back on with another reactivation).
• Show a nicer modal when deactivating a mod to prompt the user if they also want to turn off personal deployment for the mod.
• Improve the experience so that you don't have to click on activate deployment modal again right after activating.
• Avoid refetching personal deployment if it's the reactivation case with keeping it on - ideally we could just use the deployment metadata on the existing modInstance, but we currently require the entire Deployment metadata which we need to fetch from the service when activating.

Checklist

Leave all that are relevant and check off as completed

• This PR requires a security review
• This PR introduces a new library: double check it's MIT/Apache2/permissively licensed
• This PR requires a node/npm version update: let the team know on #engineering
• This PR requires a documentation change (link to old docs)
• This PR requires a tutorial update (link to old tutorials)
• This PR requires a feature flag
• This PR requires a environment variable change
• Added jest or playwright tests and/or storybook stories

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

[codecov]

Codecov Report

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

Project coverage is 75.16%. Comparing base (8318d74) to head (e1130e1).
Report is 374 commits behind head on main.

Files with missing lines	Patch %	Lines
src/activation/modOptionsHelpers.ts	81.48%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9286      +/-   ##
==========================================
+ Coverage   74.24%   75.16%   +0.91%     
==========================================
  Files        1332     1368      +36     
  Lines       40817    42243    +1426     
  Branches     7634     7866     +232     
==========================================
+ Hits        30306    31751    +1445     
+ Misses      10511    10492      -19     

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

[github-actions]

Playwright test results

 137 passed
 3 flaky
 2 skipped

Details

 Open report ↗︎
 142 tests across 46 suites
 1 hour, 10 minutes, 6 seconds
 e1130e1
 For more information on how to debug and view this report, see our readme

Flaky tests

msedge-setup › setup/unaffiliated.setup.ts › authenticate with unaffiliated user
msedge-setup › setup/unaffiliated.setup.ts › authenticate with unaffiliated user
chrome › tests/pageEditor/copyMod.spec.ts › run a copied mod with a built-in integration

Skipped tests

chrome › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options
msedge › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options

[twschiller]

Can we choose a more informative name than "handle"? E.g.:

• useUpdateOrDeletePersonalDeployment
• useCreateDeletePersonalDeployment

Potentially even calling out that it's to sync that state with the backend, e.g., useUpdateOrDeletePersonalDeploymentOnServer

[fungairino]

Since it will create, delete, fetch and in the future update personal deployments, I think a more succinct name like: useManagePersonalDeployment works here.

[twschiller]

LGTM - see suggestions on naming, dead code, and typescript failures

[github-actions]

When the PR is merged, the first loom link found on this PR will be posted to #sprint-demo on Slack. Do not edit this comment manually.