MINOR - OpenMetadata OPS to load collate-service jars first

[pmbrull]

Describe your changes:

Fixes https://github.com/open-metadata/openmetadata-collate/issues/315

❯ sh openmetadata-ops.sh deploy-pipelines
Deploying Pipelines
Instantiating the Argo Service Client with server [https://localhost:2746], namespace [argo], image [openmetadata/ingestion-base:1.0.0-alpha]
Failed to deploy pipeline OpenMetadata_dataInsight of type dataInsight for service OpenMetadata
com.google.gson.JsonIOException: Failed making field 'java.time.Instant#seconds' accessible; either increase its visibility or write a custom TypeAdapter for its declaring type.

After this update:

❯ ./openmetadata-ops.sh deploy-pipelines
Deploying Pipelines
Instantiating the Argo Service Client with server [https://localhost:2746], namespace [argo], image [openmetadata/ingestion-base:1.0.0-alpha]
+--------------------------+-------------+--------------+--------+
| Name                     | Type        | Service Name | Status |
+--------------------------+-------------+--------------+--------+
| OpenMetadata_dataInsight | dataInsight | OpenMetadata | true   |
| red_metadata_TBk2z3a1    | metadata    | red          | true   |
| red_usage                | usage       | red          | true   |
+--------------------------+-------------+--------------+--------+

The idea is that in Collate we override some internal JSON classes. By loading Collate jars first in the classpath, those updated definitions take precedence when casting the types

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.