V3 API enable should check dependencies

[dk1844]

Background & Feature

Originating in #2055 (comment), the idea is that when enabling an entity, all its dependencies should be checked to be enabled as well.

Feature

Since V3 API considers entity disable/enable as a single state (going forward), dependencies of all entity versions must be checked.

Example

DatasetA v1 has schemaA v2 and mapping CR that is tied to mappingTableA v6 and also defines propertyDefinionA
DatasetA v2 has schemaBv3, no mapping CR and definespropertyDefintionB`.

DatasetA is disabled.
When trying to (re)enable it, schemaA in v2, schemaB v3, mappingTableA v6, propertyDefintionA|B (all versions) must be check to be enabled in order for DatasetA to be correctly enabled.

Proposed Solution [Optional]

Solution Ideas:

1. Utilize the fact that disabled entities fail validation? (but dependent entities failing validation for other reasons might block enabling entities)
2. Specifically create checks for the disabled state (not tied to validation itself) based on just unique entity names
3. point 2, but also checking versions because historically, there can be entities in mixed disabled/enabled state