Move to Uber mock/mockgen fork

[kimorris27]

Which issue this PR addresses:

https://issues.redhat.com/browse/ARO-4360

What this PR does / why we need it:

This PR removes our dependency on https://github.com/golang/mock and completely switches us over to using https://github.com/uber-go/mock instead for two reasons:

1. It needs to be done eventually anyway
2. It happens to fix an issue that I ran into generating mocks for some new Azure clients I added in a MIWI PR (the golang version doesn't seem to be up-to-date enough to handle generics properly in certain contexts)

Additionally, I upgrade our go-toolset container image from 1.21.11 to 1.21.13 to satisfy Uber mockgen's dependency on Go >= 1.21.12. The corresponding ADO PR is here: https://msazure.visualstudio.com/AzureRedHatOpenShift/_git/ARO.Build.Images/pullrequest/10921698

Test plan for issue:

CI and E2E

Is there any documentation that needs to be updated for this PR?

I don't think so, but let me know if you know of any.

How do you know this will function as expected in production?

E2E during the next release :D

[edisonLcardenas]

/azp run ci,e2e

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[bitoku]

It seems like we don't have go-toolset:1.21.13-1.

Dockerfile.aro-e2e:4
--------------------
   2 |     #
   3 |     ARG REGISTRY
   4 | >>> FROM ${REGISTRY}/ubi8/go-toolset:1.21.13-1 AS builder
   5 |     
   6 |     USER root
--------------------
ERROR: failed to solve: arointsvc.azurecr.io/ubi8/go-toolset:1.21.13-1: failed to resolve source metadata for arointsvc.azurecr.io/ubi8/go-toolset:1.21.13-1: arointsvc.azurecr.io/ubi8/go-toolset:1.21.13-1: not found
make: *** [Makefile:183: image-e2e] Error 1

[tsatam]

/azp run ci,e2e

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[tsatam]

/azp run ci,e2e

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[shubhadapaithankar]

LGTM

[kimorris27]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[hlipsig]

Non-blocking question.

[hlipsig]

Goutham is trying to upgrade us to go 1.22. I see they've added support for 22 recently. Any reason to merget this at 1.21 and then update to 1.22?

[kimorris27]

Discussed in Slack. We decided to merge this PR as-is since it's blocking stuff, and I'll branch off of Goutham's 1.22 working branch to prepare another 1.22 PR related to this stuff as needed.

[hlipsig]

Based on a quick conversation with Kipp to prevent merge conflicts or other strangeness we're going to merge this as is with version 1.21 of golang, then create a follow on PR using the branch from #3797 to ensure everything here works with 1.22. Since this blocks other critical work this feels like the best route.