[WIP] fix: moving the hardcoded configs in KFPv2 Launcher to configmap. Fixes RHOAIENG-1707

[amadhusu]

Which issue is resolved by this Pull Request:
Resolves https://issues.redhat.com/browse/RHOAIENG-1707

Description of your changes:
Followed Option 1 in the suggestion mentioned in kubeflow/issues/9689

We want to allow the above configs to be changed from their defaults, preferably on a per-namespace basis.

I propose we add these configs to the ConfigMap/kfp-launcher which already exists in each profile namespace to set defaultPipelineRoot.

For example, a new ConfigMap/kfp-launcher in a profile namespace might look like this:

data:
  defaultPipelineRoot: "minio://mlpipeline/v2/artifacts"
 
  ## minio endpoint config
  defaultMinioEndpoint: "minio.example.com:9000"
 
  ## minio auth configs
  minioAuthConfig: "mlpipeline-minio-artifact"
  minioAuthConfigAccessKey: "access_key"
  minioAuthConfigSecretKey: "access_key"

OPTION 1: have the kfp-launcher container read the ConfigMap/kfp-launcher
when it executes, it can pass the minio configs down as it calls objectstore.OpenBucket

Environment tested:

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amadhusu

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[HumairAK]

closing, we'll follow up with a separate (multiple) prs to resolve these.