Run e2e with various Python versions to verify Python SDK

[tenzen-y]

Signed-off-by: Yuki Iwai yuki.iwai.tz@gmail.com

What this PR does / why we need it:
As discussed in #2057 (comment), run e2e with various Python versions to verify Python SDK.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Checklist:

• Docs included if any changes are user facing

[tenzen-y]

/hold for the review

[andreyvelich]

@tenzen-y @johnugeorge Any thoughts how to keep Python versions and this version consistent:

katib/sdk/python/v1beta1/setup.py

Lines 55 to 60 in 989d3da

	"Programming Language :: Python :: 3",
	"Programming Language :: Python :: 3 :: Only",
	"Programming Language :: Python :: 3.7",
	"Programming Language :: Python :: 3.8",
	"Programming Language :: Python :: 3.9",
	"Programming Language :: Python :: 3.10",

?
Then, we can say that we test our SDK on every version that we suggested.

[johnugeorge]

I can't think of easy way to use the same versions in sync. (other than some kind of parse)

[tenzen-y]

I don't have any good idea. As @johnugeorge says, we might need to parse setup.py and workflow files.

[andreyvelich]

@johnugeorge @tenzen-y I see, let's keep the sync for minor version (3.7, 3.8, etc.) manually for now.

[andreyvelich]

/lgtm
/assign @johnugeorge

[tenzen-y]

I'm thinking of applying the same patch to the training-operator.

[johnugeorge]

/approve
/hold cancel

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johnugeorge, tenzen-y

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:

• OWNERS [johnugeorge,tenzen-y]

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