Deleting/updating a config entity and deleting a content entity should clear its values from the auto-save store

This implements the "update" part — just needs one added hook to implement this part.

I'm not sure we should be just deleting the autosave entry when an entity is updated. I realize this is an edge case but this could still result in loss of data for the user. I think in this situation it might make sense to provide the user an option to choose if they want to continue from the autosave state of the latest revision.

@balintbrews and @hooroomoo reported the following bug:

1. Add a new code component and name it “Test”
2. Add some JS code so it gets autosaved  e.g.
   

   export default function MyComponent() {
     return <h1>HELLO WORLD</h1>
   }
   

3. Use the new “Add to components” button to make the code component external.
4. Visit /xb/xb_page/1/code-editor/code/[machineName] to edit the component again (workaround to see the issue), update something to trigger an autosave.
   Check /xb/api/config/auto-save/js_component/test and it says status: FALSE

That's another symptom of the same root cause. Confirmed through manual testing.

Given how many issues we've recently been working on in the auto-save realm, including this one and the critical #3502902: Only auto-save content entities/PageRegion config entities when there are actual changes: simply previewing incorrectly causes them to appear in "Review x changes", I think it's time to carve out an explicit issue queue component for it. #3489743: Create AutoSave service and HTTP API to retrieve all entities with pending changes introduced it, and was led by @tedbow and @larowlan, so assigning to @larowlan for review.

Nice catch on the title! 😄

I'm very glad_ I asked you to review this! 😄 You managed to avoid the content entity data loss @lauriii was worried about in #3 in an elegant way while still allowing the main issue to be fixed.