chore(components): Components - De-hardcoded outputs paths in the GCP components. Fixes: #4128

[Ark-kun]

Description of your changes:
Fixes #4128

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:

  • fix(frontend): fixes empty page. Fixes #1234
    Use fix to indicate that this PR fixes a bug.
  • feat(backend): configurable service account. Fixes #1234, fixes #1235
    Use feat to indicate that this PR adds a new feature.
  • chore: set up changelog generation tools
    Use chore to indicate that this PR makes some changes that users don't need to know.
  • test: fix CI failure. Part of #1234
    Use part of to indicate that a PR is working on an issue, but shouldn't close the issue when merged.

• Do you want this pull request (PR) cherry-picked into the current release branch?

  If yes, use one of the following options:

  • (Recommended.) Ask the PR approver to add the cherrypick-approved label to this PR. The release manager adds this PR to the release branch in a batch update.
  • After this PR is merged, create a cherry-pick PR to add these changes to the release branch. (For more information about creating a cherry-pick PR, see the Kubeflow Pipelines release guide.)

[kubeflow-bot]

This change is 

[Bobgy]

@googlebot

[Bobgy]

/lgtm

Thanks!

[Ark-kun]

/test kubeflow-pipeline-postsubmit-standalone-component-test

[k8s-ci-robot]

@Ark-kun: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

• /test kubeflow-pipeline-frontend-test
• /test kubeflow-pipeline-backend-test
• /test kubeflow-pipeline-e2e-test
• /test kubeflow-pipeline-sample-test
• /test kubeflow-pipeline-integration-test
• /test kubeflow-pipeline-mkp-test
• /test kubeflow-pipeline-upgrade-test
• /test kubeflow-pipelines-sdk-python35
• /test kubeflow-pipelines-sdk-python36
• /test kubeflow-pipelines-sdk-python37
• /test kubeflow-pipelines-sdk-python38
• /test kubeflow-pipelines-tfx-python36
• /test kubeflow-pipelines-component-yaml
• /test kubeflow-pipelines-components-gcp-python27
• /test kubeflow-pipelines-components-gcp-python37
• /test kubeflow-pipelines-component-containers
• /test kubeflow-pipelines-backend-visualization
• /test kubeflow-pipeline-multiuser-test

Use /test all to run the following jobs:

• kubeflow-pipeline-frontend-test
• kubeflow-pipeline-backend-test
• kubeflow-pipeline-e2e-test
• kubeflow-pipeline-sample-test
• kubeflow-pipeline-upgrade-test
• kubeflow-pipelines-sdk-python35
• kubeflow-pipelines-sdk-python36
• kubeflow-pipelines-sdk-python37
• kubeflow-pipelines-sdk-python38
• kubeflow-pipelines-tfx-python36
• kubeflow-pipelines-component-yaml
• kubeflow-pipelines-components-gcp-python27
• kubeflow-pipelines-components-gcp-python37
• kubeflow-pipelines-component-containers

In response to this:

/test kubeflow-pipeline-postsubmit-standalone-component-test

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.

[Ark-kun]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Ark-kun

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:

• components/OWNERS [Ark-kun]

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