Util classes for building and validating schema + leia-common

[abhigun]

• Introduced leia-common module to host all the common utils classes. Moved the SchemaValidationUtils and SchemaException classes from leia-schema-validator to this module.
• Replaced SchemaValidatable annotation with a more generalized SchemaDefinition annotation for marking schema classes.
• Added annotation classes for the Qualifiers( PII, Encrypted, ShortLived) that can be added on the members of the Schema class.
• Introduced two new classes SchemaBuilder and SchemaPayloadValidator
  - SchemaBuilder: For building the schema request against a class annotated with SchemaDefinition
  - SchemaPayloadValidator: For validating a schema json payload against a specified SchemaKey
• Addressed issues in handling plain Object and Primitive Class types in SchemaValidationUtils
• Updated dependencies in leia-core and leia-schema-validator to include leia-common
• Upgraded versions across all POM files for the new release

[koushikr]

Added a few comments. A couple of high level questions, should we change the SchemaValidatable annotation to look like the following?

`@Target({ElementType.TYPE})
@retention(RetentionPolicy.RUNTIME)
public @interface SchemaDefinition {

SchemaType type() default SchemaType.JSON;

SchemaValidationType validationType() default SchemaValidationType.MATCHING;

SchemaState state() default SchemaState.CREATED;

String schemaName();

String versionId();

String namespace();

String description() default "";

Class<?>[] transformationTargets();

}`

And use the above to build the CreateSchemaRequest itself?

Roughly I'm thinking,

`
@OverRide
public Optional getDetails(Class<?> klass) {
if (null == klass) {
log.debug("No klass definition provided. Can't convert");
return Optional.empty();
}
final var schemaDefinition = klass.getAnnotation(SchemaDefinition.class);
if (null == schemaDefinition) {
log.debug("The klass {} is not annotated with SchemaDefinition. Can't convert", klass.getSimpleName());
return Optional.empty();
}
return Optional.of(CreateSchemaRequest.builder()
.schemaType(schemaDefinition.type())
.validationType(schemaDefinition.validationType())
.description(schemaDefinition.description())
.schemaName(schemaDefinition.schemaName())
.namespace(schemaDefinition.namespace())
.attributes(
FieldUtils.getAllFields(klass)
.stream()
.map(SchemaAttributeUtils::getAttribute)
.collect(Collectors.toSet())
)
.transformationTargets(
SchemaAttributeUtils.getTransformationTargets(
klass,
schemaDefinition.transformationTargets()
)
)
.build());
}

`

Also should we do SchemaUtils (Or SchemaAttributeUtils) as part of the schema-validator itself - also the ValidationUtils must move here? leia-client can use the validator as a dependency then?

[koushikr]

Same, rename this to getQualifer

[abhigun]

Done, changed it to getQualifiers

[koushikr]

Rename this to LeiaTestUtils

[abhigun]

Done

[koushikr]

Added a few comments