Implement a built-in binary update mechanism

[brgnepal]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature Request

What you expected to happen:
I would like to update my minikube version to its latest by running minikube update command.

Anything else do we need to know:
Did we had any discussion before @aaron-prindle @r2d4 ?

[brgnepal]

Any comments @r2d4 ? It seems we just notify users that there is latest version of binary is available during minikube start.

[r2d4]

This sounds good to me, as long as it still respects the environment variable to surpress it.

[brgnepal]

This sounds good to me, as long as it still respects the environment variable to surpress it.

@r2d4 I didn't get by this comment 😄 . I am just changing the UX here by giving option to user to run minikube update instead of downloading manually from url shown as part of update notification.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[brgnepal]

Will work on this week and send the updated PR.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale