Wire up users controller and move internal clients package to pkg

[andrewstucki]

This PR does the following things:

1. It wires up the users controller to run in v2 mode.
2. It adds the CRDs to the kustomize manifest we tell users to point to when installing CRDs.
3. It moves the internal/client package to pkg/client in anticipation of utilizing factories internally in our acceptance tests
4. It adds a WithUser method on our factory to create clients who authenticate as a given SCRAM-based for authentication verification purposes in tests.
5. It upgrades common-go and helm-charts dependencies to include some fixes

After this, the controller should be fully functional/runnable despite the acceptance tests not yet being merged. I will follow up with the acceptance test code that we can opine on the approach since it's introducing the first gherkin-based fully black-box tests.

[RafalKorepta]

NIT: I would drop that listing ACLs as it is duplicated in https://github.com/redpanda-data/redpanda-operator/pull/236/files#diff-8c966a8be080a7f0e6924dd74d9d34d294fe4c3191ed06a0ab144ff8cafba012R75

[RafalKorepta]

LGTM

[RafalKorepta]

Something went wrong. Operator v2 e2e tests are failing all over the place.

[andrewstucki]

So, not entirely sure how we can fix this without doing a helm release or hacking in some additional stuff for our v2 tests. They're failing due to the controllers not starting up properly because of permission issues on users:

E0917 12:50:00.179351 1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.29.5/tools/cache/reflector.go:229: Failed to watch *v1alpha2.User: failed to list *v1alpha2.User: users.cluster.redpanda.com is forbidden: User "system:serviceaccount:redpanda:redpanda-operator" cannot list resource "users" in API group "cluster.redpanda.com" in the namespace "redpanda"

The reason being that the test setup phase installs the operator with the latest released version of the helm chart:

redpanda-operator/src/go/k8s/kuttl-v2-test.yaml

Lines 18 to 21 in 7ac4262

	- command: helm install --set logLevel=trace --set image.tag=dev
	--set image.repository=localhost/redpanda-operator --namespace redpanda --create-namespace redpanda-operator
	redpanda/operator --set rbac.createAdditionalControllerCRs=true --set additionalCmdFlags="{--additional-controllers=all}"
	--set rbac.createRPKBundleCRs=true --wait

that means that if RBAC permissions change in the helm chart (like they need to here), we can't pass CI until we release the chart.

The RBAC PR already landed in the helm-charts repo in redpanda-data/helm-charts#1527, but since it's still unreleased the tests don't see the change. Ideally we'd be installing the helm chart from the tip of the main branch and/or locally (in a monorepo).