Error Handling and Security Upgrade

1. Upgrade core-common to 0.19.0-rc9 and fix vulnerable packages
2. Error Handling when passing "%" in dataId and RecordId fields, we get generic internal server error with incorrect 500 http status code. Handled those errors with correct error code and response.

Original MR: 4326d6a5

crs-catalog-core/src/main/java/org/opengroup/osdu/crs/middleware/GlobalExceptionMapper.java

@@ -14,7 +14,7 @@
 
 package org.opengroup.osdu.crs.middleware;
 
-import io.swagger.jaxrs.config.JaxrsScanner;
+import org.eclipse.jetty.http.BadMessageException;
 import org.opengroup.osdu.core.common.logging.JaxRsDpsLog;
 import org.opengroup.osdu.crs.util.AppError;
 import org.opengroup.osdu.crs.util.AppException;
@@ -38,6 +38,13 @@ public class GlobalExceptionMapper extends ResponseEntityExceptionHandler {
         return this.getErrorResponse(e);
     }
 
+    @ExceptionHandler(BadMessageException.class)
+    protected ResponseEntity<AppError> handleBadMessageException(BadMessageException e) {
+        /*When invalid input types are passed(recordId or dataId = "%"), it causes BadMessageException.
+         Handled it with generic error with code 400 (Bad Request).*/
+        return this.getErrorResponse(new AppException(BAD_REQUEST.value(), "Bad input type or format.", "Please check the input type and format and try again."));
+    }
+
     @ExceptionHandler(Exception.class)
     protected ResponseEntity<AppError> handleGeneralException(Exception e) {
         return this.getErrorResponse(