Don't set CPU limits by default unless they are required by a LimitRange

[amisevsk]

Description

We've gotten a number of requests to not set CPU limits by default on containers. By default there is no CPU limit or request for sidecar containers, however for project-clone we do set a default CPU Limit of 1000m unless otherwise specified.

If a namespace does not include a limitRange that may require a CPU Limit to be set, we should not set one by default. If the DevWorkspaceOperatorConfig specifies a non-default CPU limit, we should use that value

Additional context

Related: eclipse-che/che#22198