Optionally delete config entities when they're deleted from code

I encountered this issue while actively developing a custom distribution. Even in a development environment, where we frequently reorganize things and delete irrelevant or incorrect configurations from features, we're somewhat blocked and have to write hook updates to manually delete configurations. It would be really helpful if config_sync could facilitate configuration deletion, similar to how it handles creation and updates—at least in a destructive manner without dependency checks, leaving that responsibility to developers for testing.