feat[frontend]: implement artifact-repositories configmap support

[droctothorpe]

Description of your changes:

Argo Workflows supports the ability to specify an artifact repository for archived logs uniquely for each namespace rather than just globally as documented here.

This PR adds support for this functionality to the KFP UI. If a workflow runs and...

1. The corresponding pods are deleted
2. The corresponding workflow is deleted
3. There is an artifact-repositories configmap in the target namespace that provides a unique, namespaced keyFormat

...this PR ensures that logs are still accessible in the UI. This functionality is disabled by default to avoid unnecessary network calls (for end users who don't leverage namespace-specific artifact-repositories). It can be toggled on through configs.ts or an environment variable.

Co-authored with @quinnovator 🌟 .

Fixes: #11339

Checklist:

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

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zijianjoy for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• frontend/OWNERS

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

[droctothorpe]

@HumairAK to recreate the edge case:

1. Deploy KFP to a local K8s cluster.
2. Set ARGO_ARCHIVE_LOGS=true in configs.ts.
3. cd into the frontend directory.
4. Run NAMESPACE=kubeflow npm run start:proxy-and-server to start the UI on your host machine.
5. Create the following configmap in the kubeflow namespace:

metadata:
  annotations:
    workflows.argoproj.io/default-artifact-repository: artifact-repositories
  name: artifact-repositories
  namespace: kubeflow
data:
  artifact-repositories: |-
    archiveLogs: true
    s3:
      accessKeySecret:
        key: accesskey
        name: mlpipeline-minio-artifact
      bucket: mlpipeline
      endpoint: minio-service.kubeflow:9000
      insecure: true
      keyFormat: foo
      secretKeySecret:
        key: secretkey
        name: mlpipeline-minio-artifact
kind: ConfigMap

6. Run a simple pipeline.
7. Once it completes, delete the AWF workflow custom resource associated with the run.
8. Try to access the logs of the run in the UI running on your host machine. On master, this operation will fail. On this branch, it will succeed.
9. The next few steps are optional. Port-forward the minio pod.
10. Navigate to the minio UI.
11. Login (username: minio, password: minio123).
12. Note how the logs are stored in mlpipeline/foo rather than the default keyFormat specified in configs.ts. Argo grants precedence to the keyFormat specified in the artifact-repositories configmap over the keyFormat specified in workflow-controller-configmap.

[droctothorpe]

I updated the instructions to reproduce to edge case to make manual validation a lot easier by running the UI on your host machine.