feat(deployment): Add env/platform-agnostic-pns standalone deployment option

[Gsantomaggio]

Description of your changes:
Add containerRuntimeExecutor explicit type on workflow-controller-configmap.yaml configuration.
docker is the default.
platform-agnostic-pns type configuration needed by Kind, K3s and Minikube.
Part of #4256
Related to: kubeflow/website#2056

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.

  PR titles examples:

  • feat(deployment): configurable containerRuntimeExecutor fixes (part of) Document how to run KFP on local Kubernetes cluster like Kind, k3s, minikube #4256

example new PNS feature:

kubectl kustomize  manifests/kustomize/env/platform-agnostic-pns | grep containerRuntimeExecutor -A 5
  containerRuntimeExecutor: pns
  dbHost: mysql
  dbPort: "3306"
  mlmdDb: metadb
  pipelineDb: mlpipeline
kind: ConfigMap
--
    containerRuntimeExecutor: pns,
    artifactRepository:
    {
        s3: {
            bucket: mlpipeline,
            keyPrefix: artifacts,

example with docker feature:

 kubectl kustomize  manifests/kustomize/env/platform-agnostic | grep containerRuntimeExecutor -A 5
  containerRuntimeExecutor: docker
  dbHost: mysql
  dbPort: "3306"
  mlmdDb: metadb
  pipelineDb: mlpipeline
kind: ConfigMap
--
    containerRuntimeExecutor: docker,
    artifactRepository:
    {
        s3: {
            bucket: mlpipeline,
            keyPrefix: artifacts,

[kubeflow-bot]

This change is 

[k8s-ci-robot]

Hi @Gsantomaggio. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Bobgy]

/lgtm
other than the only one comment

Thank you for your contribution!

[Bobgy]

Thought of one more comment

[Gsantomaggio]

@Bobgy @alfsuse it should be ready now!

[Bobgy]

Thank you! I think this is great!
/ok-to-test
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

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

The pull request process is described here

Needs approval from an approver in each of these files:

• manifests/kustomize/OWNERS [Bobgy]

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

[Gsantomaggio]

@Bobgy some test failed, but I am not sure is related to my changes. I trying to understand btw

[Bobgy]

/retest

I don't think they are related.

[Bobgy]

/retest

[rmgogogo]

/lgtm

assume we won't bring it to MKP and I personally prefer no.