Adding component to component library results in component code and configuration being lost

I took a look, and what happens here is that if we use the contextual menu from the sidebar list, we will send the canonical entity data with the PATCH request when we update the JavaScriptComponent entity to rename it or make it internal/exposed, because that's what we have available in the React component that outputs that list. With a new code component which hasn't been published since it was created, it means that only the auto-saved version has the data — and we lose all of that. 🙈

This isn't a cache invalidation problem, because the endpoint that lists the code components doesn't use auto-saved data. To solve the issue, we need to:

1. Fix 🐛 PATCH request for config entities reset values that are not sent Active (priority increased)
2. Update our PATCH requests to include only the wanted changes:
   • ui/src/features/code-editor/dialogs/AddToComponentsDialog.tsx
   • ui/src/features/code-editor/dialogs/RemoveFromComponentsDialog.tsx
   • ui/src/features/code-editor/dialogs/RenameCodeComponentDialog.tsx

🐛 PATCH request for config entities reset values that are not sent Active is in!