Update Transformer API to use common OSDU patterns for auth and responses

Type of change

• Bug Fix
• Feature
• Refactoring

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [YES] HTTP status code of the Ambassador API Calls are updated.

What is the current behavior?

• Current Authorization is manually handled and flawed as the provided userEmail in the QueryString is never validated against the current authenticated user.
• Authorization and input validation is manually handled instead of using Spring Annotation like it's done in the core OSDU services