Conditional field configurations persist after entity type is deleted

Problem/Motivation

When an entity type (e.g., paragraph type) is deleted, the Conditional Fields module does not clean up the associated configuration data. This results in orphaned configurations remaining in the system and routes to non-existent entity types still functioning.

Example: After deleting the experience_price paragraph type, navigating to /admin/structure/paragraphs_type/experience_price/conditionals still works and displays the conditional field configurations.

Steps to reproduce

Create a paragraph type (e.g., "experience_price")
Add fields and configure conditional field states at /admin/structure/paragraphs_type/experience_price/conditionals
Delete the entire paragraph type
Navigate to /admin/structure/paragraphs_type/experience_price/conditionals
Expected result: 404 error or appropriate message indicating the entity type no longer exists

Actual result: Configuration page loads successfully with orphaned configurations

Proposed resolution

Implement entity type/bundle deletion hook to remove associated conditional field configurations
Add route access validation to prevent access to configuration pages for non-existent entity types
Provide cleanup utility for existing orphaned configurations

User interface changes

Conditional field configuration pages for deleted entity types will return 404 or show an error message.