Gradual transition to one CI pipeline for Partition

This MR created for necessary changes to adhere the acceptance criteria of this Issues: https://gitlab.opengroup.org/osdu/pmc/community-implementation/-/issues/101

Key changes:

• Introduced the Maven Profiles and its configuration
• Set the core profile as default

changed milestone to %M25 - Release 0.28

added Platform Standardization label

requested review from @Rustam_Lotsmanenko

assigned to @mfaidluqman

approved this merge request

removed milestone %M25 - Release 0.28

approved this merge request

approved this merge request

merged

mentioned in commit f70f68f3

Hello @Rustam_Lotsmanenko, when you do modify the AWS buildspec.yaml, can you also modify it to match what is in this MR?

This still caused a failure in the AWS internal build. We are working internally to externalize these buildspec.yaml files from the repositories, but that likely won't be done before you have finished making the migrations to the one CI pipeline.

Hi, @dhudsons, yes, I'm sorry for that, I haven't spotted that we doing it wrong. Luckily we don't have many left. To be honest I'm still not sure how the AWS external build should look because here we don't use the core profile and Marc approved it, but in your example core profile is used.

May I ask you to recheck open MRs?

osdu/platform/data-flow/ingestion/csv-parser/csv-parser!499 (merged)

osdu/platform/data-flow/ingestion/external-data-sources/eds-dms!212 (merged)

indexer-service!871 (merged)