Update Resources

This may need some more testing and/or be able to be slimmed down further. The problem only seems to present itself on RKE2 nightly pipeline, not on the k3d CI one or local dev with k3d.

Through on the fly testing with the infra pipeline (see https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/855) this is the number I arrived at that seemed to work well. 200m CPU resulted in issues and it seemed like the same was true with memory.

See https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/sonarqube/-/issues/10 for context.