Add blocklist to NameRes

[gaurav]

We are implementing a Blocklist in Translator at https://github.com/NCATSTranslator/Blocklists, which will consist of a list of CURIEs that must be excluded from NameRes. This PR implements this by modifying the NameRes restore job in three ways:

1. By creating an ephemeral storage volume (whose size is determined by the blocklist.storage config) to store the Blocklist.
2. By adding support for a GitHub Personal Access Token (stored as a Kubernetes secret whose name is determined by the blocklist.github_personal_access_token_secret variable, and whose key is fixed as github_personal_access_token), which will be used to download the Blocklist file if it is in a private GitHub repository.
3. By modifying the restore.sh script in to download the Blocklist file (as a text file containing a list of CURIEs, one on each line, as specified by the blocklist.url config), convert it into a string of double-quoted CURIEs, build a delete query for deleting all of these CURIEs, and then execute it.

Also includes:

• The correction to the default NameRes version and data file from PR Fix NameRes version and source #723
• An increase to the memory available to the id-id table, since we now have more IDs.

[YaphetKG]

If the github access token is needed by all the instances(ci test, and prod) after this and if its going to be the same across them, maybe we need to save it in values-populated.yaml ,
which is encrypted aswell , and intended to use common values accross envs

[gaurav]

If the github access token is needed by all the instances(ci test, and prod) after this and if its going to be the same across them, maybe we need to save it in values-populated.yaml , which is encrypted aswell , and intended to use common values accross envs

Thanks for the suggestion, @YaphetKG! I've updated the template to set up a Kubernetes Secret based on the value stored in the values-populated.yaml file as you suggest.

[YaphetKG]

LGTM!