…e contours, empty DatasetControllerV3 to test

 - login allowed at /api/login & /api-v3/login
 - v2/v3 BaseRestApiTest distinquished

…st cases added

…der and no content -> IT updated

… IT updated

…version, includes a sample CR)

…st and post-import + IT to prove correct behavior

…mport + IT to prove correct behavior - fix with common location processing with segment stripping (+normalization)

… GET datasets/{name}/{version}

…/audit-trail added

…ion} now works for # or 'latest' (IT = regression test)

…{name}/{version} and /{name}/latest - improved

…- supports latest for as version-expression, impl for datasets improved by actual existence checking + IT test cases for non-existing/non-latest queries

…properties - supports latest for as version-expression; get impl is unvalidated, put impl checks validity

 - login is now common, under /api/login for both v2 and v3 (did not work previously)

…properties - supports latest for as version-expression; get impl is unvalidated, put impl checks validity - extended for different validation cases

 - login is now common, under /api/login for both v2 and v3 (did not work previously)

…ture -> CompletableFuture (mistake reverted)

… added. IT mostly adjusted, but there are todos

 - DatasetServiceV3 introduced to carry difference in behavior to DatasetService. original entity validation has been divided into create-validation and regular-entity validation.
 - buildfix for VersionedModelServiceTest

…sion}` in proper validations

…asets/dsName/version/rules, GET datasets/dsName/version/rules/# + IT

 - v2 ignores this added information
 - needs

…api-v3-schema-etc

…api-v3-schema-etc

…defaults

…ts + IT

…api-v3-schema-etc

…l, .../from-file

VersionedModelControllerV3 now requires admin rights on specific endpoints (create, edit, import, delete) - TODO reflect in other datatypes

…d in DatasetControllerV3, MappingTableControllerV3, SchemaControllerV3. ITs fixed, but 403 tests missing

… 403 cases for all types

…y fields + PUT/POST with schema with empty fields -> 400 validation error, too. + ITs reflecting this (this reqiured parallel SchemaServiceV3)

…s to the implementation of V3 alongside of V2

… (PUT .../{name}) implemented. ITs cover dataset disabling

 - BaseRestApiTest omits entity for Delete calls + reflected in various places

…name}/used-in & /{name}/{version}/used-in). The former is used in disable checking.

IT cases added for Schema usedIns, Datasets with disabled entities

… test cases.

…api-v3-schema-etc

…3-delete-recreate

…xtensible via `updateFields` method - V3 uses this to reflect schema fields (actual name of the field :D).

…3-delete-recreate

…s for usedIn and delete added.

Custom alternative:
```scala
//  /**
//   * Finds references of MappingTable in Dataset's mapping conformance rules
//   * @param mtName
//   * @return
//   */
//  def findRefByMappingTableInMappingConformanceRules(mtName: String, version: Option[Int]): Future[Seq[MenasReference]] = {
//    /* The gist of the find query that this method is based on; testable in a mongo client
//      { $and : [
//        {...}, // non disabled
//        {"conformance": {"$elemMatch": {$and : [
//          {"_t": "MappingConformanceRule"},
//          {"mappingTable": "AnotherAwesomeMappingTable"} // mappingTableVersion not needed for match, but will be reported as part of the MenasReference
//        ]}}}
//      ]}
//     */
//    val versionFilter = version.fold(Filters.and() /*empty filter*/ )(ver => Filters.eq("mappingTableVersion", ver))
//
//    val filter: Bson = Filters.and(
//      getNotDisabledFilter,
//      Filters.elemMatch("conformance", Filters.and(
//        Filters.eq("_t", "MappingConformanceRule"),
//        Filters.eq("mappingTable", mtName),
//        versionFilter
//      ))
//    )
//
//    collection
//      .find[MenasReference](filter)
//      .projection(fields(include("name", "version"), computed("collection", collectionBaseName)))
//      .sort(Sorts.ascending("name", "version"))
//      .toFuture()
//  }
```

… between None and Some(Seq.empty) in various places, V3 consistently returns None for no references groups -> reflected in V3 ITs. + cleanup

…vice and DatasetServiceV3 with renaming.

VersionList removed in favor of VersionedSummary everywhere.
- explanatory comments

…api-v3-schema-etc

…3-delete-recreate

% Conflicts:
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/services/v3/DatasetServiceV3.scala

…rt mapping removed -> reflected in IT; small updates

… removed, some ITs and comments added

…rt mapping removed -> reflected in IT; small updates

… removed, some ITs and comments added

…api-v3-schema-etc

…3-delete-recreate

…ing,

…3-delete-recreate

…authentication)")` is now limited to changing endpoints of PropertyDefinitionControllerV3 (previously it was incorrectly used for all changing endpoints. IT updated. And specific check for the adminRole have been added to PropertyDefinitionControllerV3IntegrationSuite.

…3-delete-recreate

% Conflicts:
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/v3/PropertyDefinitionControllerV3.scala
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/v3/VersionedModelControllerV3.scala
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/DatasetControllerV3IntegrationSuite.scala
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/PropertyDefinitionControllerV3IntegrationSuite.scala

…g `dev` or not.

…api-v3-schema-etc

…3-delete-recreate

…api-v3-schema-etc

…3-delete-recreate

…ion`. Small updates, thanks @benedeki

… with `MappingTableControllerV3.withMappingTableToResponse`

…3-delete-recreate

% Conflicts:
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/SchemaController.scala
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/v3/VersionedModelControllerV3.scala
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/services/SchemaService.scala
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/services/VersionedModelService.scala
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/DatasetControllerV3IntegrationSuite.scala

…3-delete-recreate

% Conflicts:
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/DatasetControllerV3IntegrationSuite.scala

% Conflicts:
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/v3/PropertyDefinitionControllerV3.scala
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/services/v3/MappingTableServiceV3.scala
%	rest-api/src/main/scala/za/co/absa/enceladus/rest_api/services/v3/SchemaServiceV3.scala
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/MappingTableControllerV3IntegrationSuite.scala
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/PropertyDefinitionControllerV3IntegrationSuite.scala
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/SchemaControllerV3IntegrationSuite.scala

…bled` information - mainly on GET ...{/name}

…tion. IT updated.

 - custom isDisabledCheck is not needed anymore (V3 services use `validate` for this)
 - `EntityDisabledException` removed, replaced by a `Validation` with `disabled` key.
 - validation fixed for Schemas (did not include super-check)
 - V3 integTests updated to cover the `disabled` = validation fail

…api-v3-disabled-fails-validation

…api-v3-disabled-fails-validation

… an error message (`UsedIn` wrapped in `EntityInUseException`)

…api-v3-disabled-fails-validation

% Conflicts:
%	rest-api/src/test/scala/za/co/absa/enceladus/rest_api/integration/controllers/v3/MappingTableControllerV3IntegrationSuite.scala

…, cleanup

…api-v3-disabled-fails-validation