Unavailable deployments not uninstalled on Extension Console refresh

[twschiller]

Describe the bug

• Unavailable deployments are not uninstalled when the Extension Console loads
• Caused a high priority customer support issue on 4/1/2024
• https://pixiebrix.slack.com/archives/C0436P48QHY/p1712003575025649

To Reproduce

Steps to reproduce the behavior:

1. Create a deployment with a group
2. Refresh the Extension Console
3. Pause the deployment and immediately remove the group from the deployent (marking as paused is likely not required to replicate, but is what the customer did)
4. Refresh the Extension Console

Actual behavior

1. The deployment is still installed

Expected behavior

1. The deployment is automatically uninstalled after the assigned deployments are fetched

Desktop (please complete the following information):

• Extension Version: 1.8.11

Workaround

• Close the extension console and wait 5 minutes for the next heart beat, or
• Toggle off/on the browser extension to force a background heartbeat

Discussion

• https://pixiebrix.slack.com/archives/C0436P48QHY/p1712003575025649

Related Issues

• Switching the mod in a deployment leaves both activated #7475

Related Code

• pixiebrix-extension/src/background/deploymentUpdater.ts

  Line 171 in 73072cc

  async function uninstallUnmatchedDeployments(

Implementation Sketch

• Calculate removed deployments in the derived state:

  pixiebrix-extension/src/extensionConsole/pages/deployments/DeploymentsContext.tsx

  Line 116 in 73072cc

  const deploymentUpdateState = useDeriveAsyncState(

• Create a useRemoveDeploymentsEffect hook and pass the unavailable deployments. NOTE: be careful to only remove the unavailable deployments if the deployments request succeeded (i.e., the set of deployments is known)

[twschiller]

@grahamlangford based on @mnholtz investigation these 2 issues likely have the same root cause and should likely be worked on together: #7475