docs: clarify python client installation steps

[Crazyglue]

Description

When doing a fresh install of the python client for local development, I ran into an issue where dependencies would install, but there would be a bunch of unformatted files in my git working directory. After some checking it appears after a make install you need to run make tidy to format everything. This is already encapsulated in the Makefile as all: install tidy, so all thats actually needed is to just run make.

This updates the README.md to clarify this point

How Has This Been Tested?

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages; the author will squash them after approval or in case of manual merges will ask to merge with squash.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.

If you have UI changes

• The developer has added tests or explained why testing cannot be added.
• Included any necessary screenshots or gifs if it was a UI change.
• Verify that UI/UX changes conform the UX guidelines for Kubeflow.

[Al-Pragliola]

/lgtm

[tarilabs]

thanks a lot @Crazyglue and all for 👀

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Al-Pragliola, tarilabs

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 [tarilabs]

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