Use docker buildx 0.8.x --no-cache-filter to avoid using cached amazonlinux image

[wongma7]

Is this a bug fix or adding new feature? /feature

What is this PR about? / Why do we need it?
When building image, always run yum update -y and avoid using whatever amazonlinux image/layer is in the cache because it might be outdated.

--no-cache-filter requires buildx 0.8.x which just came out in March https://github.com/docker/buildx/releases/tag/v0.8.0

there is another flag --no-cache that is available in earlier versions but I DON'T want to use that because it means that the windows layers don't get cached and those take a LONG time to build.

We need to build new images frequently to keep up with CVEs in amazonlinux image. At least until we switch to a "minimal" image that has less surface area for CVEs.

What testing is done?

make image works and yum update -y is always run, it's not cached.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wongma7

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

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

[wongma7]

/assign @torredil

[k8s-ci-robot]

@wongma7: GitHub didn't allow me to assign the following users: torredil.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @torredil

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.

[torredil]

cc @gtxu

[gtxu]

/lgtm