De-hardcode output paths in IBM components

[Ark-kun]

See the parent issue: #4100

Some components are using the deprecated fileOutputs attribute. See the query

The fileOutputs was deprecated from the start and should not be used in any non-legacy components.

We need to migrate from the deprecated fileOutputs to use the correct {outputPath: output_name} command-line placeholders instead.

Example:

Before:

implementation:
  container:
    command:
    - my_prog.py
    - --param1
    - value1
    fileOutputs:
      some_output: /some/hardcoded/path

After:

implementation:
  container:
    command:
    - my_prog.py
    - --param1
    - value1
    - --some-output
    - {outputPath: some_output}

The component code should be modified to receive all output paths through command-line arguments instead of hard-codong any paths.

An example of the correction: https://github.com/kubeflow/pipelines/pull/580/files#diff-9c31c4b41f436d2bbdfc9c97d40b9fe1
https://github.com/kubeflow/pipelines/pull/580/files#diff-ec0c67e038e3087e2bb01d439771bddc

[animeshsingh]

/assign @Tomcli

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[Bobgy]

/reopen
/frozen

[k8s-ci-robot]

@Bobgy: Reopened this issue.

In response to this:

/reopen
/frozen

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.

[jizg]

@animeshsingh @Tomcli I think I can help on update the codes for this issue. But I may need some guide on how to do the tests for IBM components. Thanks.