chore(sample): upgrade katib and kfp sdk versions in e2e mnist tutorial

[zijianjoy]

Description of your changes:

To prepare for kubeflow 1.4 release

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.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[andreyvelich]

Thank you for the update @zijianjoy!
/lgtm

[zijianjoy]

/retest-required

[chensun]

Just curious, what was breaking before the sdk upgrade?

[zijianjoy]

@chensun There was a new version of katib coming out, and I am preparing the Kubeflow 1.4 release, which carries KFP 1.7 backend along. Therefore I am upgrading katib and KFP to encourage users to adopt the latest change of both SDKs.

[chensun]

@chensun There was a new version of katib coming out, and I am preparing the Kubeflow 1.4 release, which carries KFP 1.7 backend along. Therefore I am upgrading katib and KFP to encourage users to adopt the latest change of both SDKs.

I see. The title made me think there was something to be fixed, and it's not clear to me what we have changed in the SDK could potentially affect this sample.
I would probably use chore(sample) instead.

/lgtm

[zijianjoy]

@chensun You are right, it is my bad to use fix here. Updated to chore, thank you Chen!

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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:

• samples/contrib/kubeflow-e2e-mnist/OWNERS

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