feat(sdk): add experiment_id parameter to create run methods

[droctothorpe]

Description of your changes:
Currently, create_run_from_pipeline_func and create_run_from_pipeline_package accept an experiment_name parameter and lookup the experiment ID with a backend call via create_experiment.

This tiny PR lets users pass the experiment ID directly as an optional alternative, circumventing the extra call, and improving alignment between these methods and create_recurring_run.

It also decouples the experiment handling logic from the run name handling logic. They were interleaved previously.

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.

[google-oss-prow]

Hi @droctothorpe. 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.

[droctothorpe]

/assign @connor-mccarthy

[connor-mccarthy]

@gkcalat @chensun, I seem to recall some discussion around particular parts of the API having trouble with requests that specify an experiment ID. It's possible I'm misremembering. Could you let me know if this sounds familiar?

/ok-to-test

[droctothorpe]

FWIW, the run_pipeline invocation receives an experiment ID, it's just preceded by an ID lookup via create_experiment when the experiment name is passed.

[gkcalat]

As for the backend, a run in v1 API could have a resource reference to a parent experiment. In v2, the Run message got experiment_id field. If it's missing, the backend will assign the run to the default experiment. If the default experiment is missing (not created), then the BE will throw an error.

In v2, we recently marked experiment_id field outside of the Run message in CreateRunRequest as deprecated to align it with resource hierarchy logic in v1. experiment_id inside the Run should be set by SDK.

Adding a reference to the parent experiment by ID instead of name in v1 makes sense to me.

[droctothorpe]

Addressed the yapf finding. Are the other test failures unrelated?

[chensun]

/lgtm

[google-oss-prow]

@droctothorpe: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
kubeflow-pipelines-sdk-execution-tests	4c9d4f5	link	true	/test kubeflow-pipelines-sdk-execution-tests

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. I understand the commands that are listed here.

[chensun]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chensun

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:

• sdk/OWNERS [chensun]

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