Make "limits" optional

The internet recommends removing CPU limits from the configuration. and only specifying memory limits.

[For the love of god, stop using CPU limits on Kubernetes](https://home.robusta.dev/blog/stop-using-cpu-limits/)
[Kubernetes CPU Throttling: The Silent Killer of Response Time](https://community.ibm.com/community/user/aiops/blogs/dina-henderson/2022/06/29/kubernetes-cpu-throttling-the-silent-killer-of-res)
[Kubernetes: Make your services faster by removing CPU limits](https://erickhun.com/posts/kubernetes-faster-services-no-cpu-limits/)
[CPU limits and aggressive throttling in Kubernetes](https://medium.com/omio-engineering/cpu-limits-and-aggressive-throttling-in-kubernetes-c5b20bd8a718)

suggestion is to comment out the default cpu values in the chart, and also add if defined to include the parameters

Inspect the Helm chart's default CPU values and the template that includes resource parameters. Make CPU limits optional while retaining memory limits when configured, then render the chart with and without CPU values to verify the generated configuration.

Written by the indexing model from the issue text.