Update registries and services links not working - changing FAIRsharing API

The workflow for updating registries keeps failing due to a rate limit coming from our FAIRsharing's firewall (not the application server).

The FAIRsharing team is suggesting moving away from the REST API, which requires a token refresh and also puts a greater load on our server. For searching records, it is you recommended using the GraphQL API, which has recently become available. One could then use the [*advancedSearchFast* query ](https://api.fairsharing.org/schema/query.doc.html), which uses only *Elasticsearch*; this is much quicker and also reduces the load on the server.

The key for using this service has already been added to RDMkit's profile on FAIRsharing, and it is visible there.
The said key should be sent in the POST headers as *X-GraphQL-Key*.

Start by locating the workflow that updates registries and the current FAIRsharing REST API calls. Read the advancedSearchFast query documentation and verify how the X-GraphQL-Key POST header is supplied. Done means registry and service links update successfully without the current rate-limit failure.

Written by the indexing model from the issue text.