fix orchestratord helm chart resources

[alex-hunt-materialize]

Fixes orchestratord helm chart resources specification.

1. Memory requests should always be equal to limits, as memory can generally not be reduced without killing the pod.
2. Limiting CPU is usually not useful, and prevents us from spiking briefly in periods of extremely rare load.
3. The indentation when templating the resources was a bit too deep.

Motivation

Part of https://github.com/MaterializeInc/cloud/issues/10285

Tips for reviewer

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.