bump brew version to v0.20.8

[abhinavmpandey08]

Issue #, if available:

Description of changes:

Testing (if applicable):

Documentation added/planned (if applicable):

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[abhinavmpandey08]

/approve

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavmpandey08

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

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

[pokearu]

/lgtm
/meow

[eks-distro-bot]

@pokearu:

In response to this:

/lgtm
/meow

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.

[abhinavmpandey08]

/cherry-pick release-0.20

[eks-distro-pr-bot]

@abhinavmpandey08: #8893 failed to apply on top of branch "release-0.20":

Applying: bump brew version to v0.20.8
Using index info to reconstruct a base tree...
M	release/triggers/brew-version-release/CLI_RELEASE_VERSION
Falling back to patching base and 3-way merge...
Auto-merging release/triggers/brew-version-release/CLI_RELEASE_VERSION
CONFLICT (content): Merge conflict in release/triggers/brew-version-release/CLI_RELEASE_VERSION
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 bump brew version to v0.20.8
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.20

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.