Preformance enhancement for security checking (#6697)

[mandy-chessell]

Description

This PR makes the change suggested in #6697. Essentially the formating of the asset and connection bean for calls to the security connector now occur after the metadata-security module has determined there is a security connector to call rather than on every request. It will make no difference to a server running the security connector. Those servers not running the security connector will run faster. The other benefit is that the bean formatting code has moved from the generic handler to the metadata security module which is better modularization.

During the testing I spotted that the generic handlers were checking that the qualified name is unique twice during the create call. This is an expensive check to make since it requires a query to the cohort so removing the second check will improve performance on the create.

Fixing this bug meant the parameters that pass the unique parameter on the create bean call were no longer needed and so this method no longer has these parameters and all of the callers have been updated.

Other bugs I discovered were that the ValidValuesImplementation relationship, which should be multi-link was using the uni-link creation method which means that the second mapping relationship for a code table will fail. This will impact the GHC issue odpi/egeria-samples-api#8 which will require this fix to run.

Finally I updated the type archive for release 3.12

Related Issue(s)

#6697

Testing

FVT and the open metadata labs

Release Notes & Documentation

Just internal

Additional notes

[mandy-chessell]

Final commit adds a new type called RootSchemaType. This is inserted in the SchemaType inheritance hierarchy for the schema types that connect the schema to the asset/port etc. See models 53xx for its use.