Kustomize: Correctly use resources instead of bases

[terencecho]

What

Kustomize was recently changes to use resources instead of the deprecated bases in this PR: #14037.

The acceptance tests have been broken because of this change. This PR is an attempt to fix that.
The error that shows up is:

Applying dev-integration-test manifests to kubernetes...
error: rawResources failed to read Resources: Load from path ../../resources failed: '../../resources' must be a file (got d='/actions-runner/_work/airbyte/airbyte/kube/resources')
Error: Process completed with exit code 1.

The fix will probably require changing the structure of the files to follow something like this: https://kubectl.docs.kubernetes.io/guides/config_management/components/.

[terencecho]

i think the problem is running into this issue:
kubernetes-sigs/kustomize#776 (comment)

[terencecho]

My hypothesis is that we're using Kustomize v2 which doesn't support resources as directories, instead of v3. Reverting seems to be the best course of action while we confirm that's the case and upgrade / figure out what the root cause of the failing acceptance tests are.

[terencecho]

Looks like we're utilizing the latest kubectl which should have v4 of Kustomize as outlined here.

Also, from the official kubernetes documentation, they still use bases instead of resources: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/#bases-and-overlays

[terencecho]

todo: remove the moved resources and revert the forced acceptance test runs

[terencecho]

The base resources need to be in the same parent dir as the overlays if we're using Resources instead of Bases.
Nvm, that doesn't fix the issue.

[terencecho]

we probably need to separate it out into components: https://kubectl.docs.kubernetes.io/guides/config_management/components/