Fix the build/README.md documentation file on docker-machine remote

[adeniyistephen]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Remove docker-machine / remote docker support from build documentation.

Docker-machine is no longer accepting new features and in maintenance mode only. So documentation was updated.
Which issue(s) this PR fixes:
Part of #94091.

@jherrera123 worked on the build script so here is the updated documentation for the build.

Does this PR introduce a user-facing change?:

Official support to build kubernetes with docker-machine / remote docker is removed. This change does not affect building kubernetes with docker locally.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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.

[k8s-ci-robot]

Welcome @adeniyistephen!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @adeniyistephen. Thanks for your PR.

I'm waiting for a kubernetes 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.

[jesusha123]

/ok-to-test

[jesusha123]

/sig testing
/sig release

[adeniyistephen]

/sig testing
/sig release

[adeniyistephen]

@jherrera123 PTAL how is it? i mistakenly closed and reopen it.

[jesusha123]

Looks good.

You can copy the release notes from my PR. This change has user facing changes (removal of docker machine/remote support).

[adeniyistephen]

Looks good.

You can copy the release notes from my PR. This change has user facing changes (removal of docker machine/remote support).

check is that it?

[jesusha123]

/lgtm

[fejta]

/lgtm
/approve

[fejta]

/hold

[fejta]

/hold cancel
(release note already generates a hold)

[spiffxp]

Updated PR description to add release-note block

/hold
Is there any code that needs to be removed?

[spiffxp]

/hold cancel
Looks like #97618 removed the relevant code

[spiffxp]

/priority important-soon
/triage accepted
/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adeniyistephen, fejta, spiffxp

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:

• build/OWNERS [fejta,spiffxp]

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