Update import workers to set memory resource boundary

What does this MR do and why?

In gitlab-com/gl-infra/k8s-workloads/gitlab-com!2626 (comment 1338660123) updated Workers were moved from imports to memory-bound shard. As suggested by Sean, instead of updating the k8s config manually in k8s-workloads repo, we can just update the workers in gitlab cobease itself. More visible and less maintenance this way.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.