Prevent config components from being deleted if they are used in an Experience Builder field

We should be able to remove pattern from the list because patterns are not leaving any references to the config entity; they are always stored as a copy.

Same problem exists for SDCs; there's nothing preventing them from being deleted from the code base 💬 ComponentNotFoundException: Unable to find component Active .

This is obsolete now, after:

• 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active
• 📌 [later phase] Support props defaults that have config dependencies Postponed
• 🐛 Cannot delete JS components due to component depending on them Active

Together, they fully solve this, and even more deeply than described here.

💬 ComponentNotFoundException: Unable to find component Active still is open (and has a more precise title now)