Handle wildcard parameter in Schema deletion API

[ThomasCAI-mlv]

No description provided.

[loicgreffier]

@ThomasCAI-mlv Linking #447. Note that notFound is thrown when version does not match among all the schemas

[ThomasCAI-mlv]

I adopted your errorHandling structure for "notFound" and "dryRun" cases.

As discussed together in case of deletion of version:

1. I removed the ownership checker, as we don't want to restrict the usage of wildcard by forcing users to type the namespace prefix. The findByWildcard already filters the namespace's resources.

2. We prefer anyMatch over allMatch to be homogeneous with other DELETE endpoint:

• Deleting multiple connect clusters including at least one with connectors will lead to "ResourceValidationError"
• Deleting multiple namespaces including at least one with resources inside will lead to "ResourceValidationError"
  So we can also implement the schema version deletion and throw "notFound" if at least one version doesn't exist.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[loicgreffier]

LGTM