incorrect handling of /description profiles

[Frosty2500]

Currently when a tested server supports the full feature set of a profile and not just the read operations the /description test fails. This does not make much sense since the server supports all required routes and more.

Example:

  Invoke /description
            Response: (200): {"profiles":["https://admin-shell.io/aas/API/3/1/AssetAdministrationShellRepositoryServiceSpecification/SSP-001","https://admin-shell.io/aas/API/3/1/SubmodelRepositoryServiceSpecification/SSP-001"]}
            Check
               Check meta model
               Check constraints
            Contains https://admin-shell.io/aas/API/3/0/AssetAdministrationShellRepositoryServiceSpecification/SSP-002: Fail