Explore if Workhorse API limits should be pinned to Puma thread count automatically
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=325809)
</details>
<!--IssueSummary end-->
While working on adding Hybrid Reference Architecture support to GET [it was suggested that the `apiLimit` argument along with some others should be set for Workhorse to be close to total Puma thread count](https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/merge_requests/163#note_522354462):
```
-apiLimit 11 -apiQueueLimit 200 -apiQueueDuration 60s
```
If this is indeed recommended then it's better to be set automatically in Omnibus (and Charts) so everyone can benefit. Since Puma thread count in Omnibus is set automatically Workhorse API limits should be the same.
issue