Investigate modifying our CI FE nodes to leverage the new internal API endpoint
<!--
This template is for GitLab Team Members seeking support of SRE where there isn't an existing `request-*` template available.
Please fill out the details below.
-->
**Details**
- Point of contact for this request: [+ @user +]
- If a call is needed, what is the proposed date and time of the call: [+ Date and Time +]
- Additional call details (format, type of call): [+ additional details +]
**SRE Support Needed**
At closure of Epic: https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/879, we'll have an internal API endpoint that can be leveraged for more stuff. Currently the epic is only addressing the production-engineering~20421380, but ~"Service::CI Runners" is another potential candidate that can take advantage of this.
The primary benefit of this change is reducing the amount of traffic being sent to the customer facing API endpoint for internal services. We can use the aforementioned epic for inspiration. Implementation will significantly differ as we'll need to change which endoint the CI FE nodes are looking at.
#### References:
* https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/blob/358ee14064168478ba6612a38929332f5e8b30bf/roles/gprd-base-lb-fe-config.json
* https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/blob/master/roles/gprd-base-lb-fe-ci.json
<!--
please do not edit the below
-->
issue