feat(sessions): irn client scaffolding

[geekbrother]

Description

This PR implements the IRN client abstraction into the blockchain-api. The following changes are made:

CI/CD and build

• WalletConnect/irn-node repository was added as a git submodule.
• irn_api and network packages were added as dependencies from the irn-node.
• BSL-1.0 license was added to the allowed list.

The following IRN client configuration parameters were added:

• RPC_PROXY_IRN_NODE environment variable and irn_node terraform variable for the IRN node address to connect to in IP:Socket format.
• RPC_PROXY_IRN_KEY environment variable and irn_key terraform variable for the IRN client private key.
• RPC_PROXY_IRN_NAMESPACE environment variable and irn_namespace terraform variable for the IRN storage namespace.
• RPC_PROXY_IRN_NAMESPACE_SECRET environment variable and irn_namespace_secret terraform variable for the IRN storage namespace secret.

The following IRN client storage commands were added:

• Key-value storage set,get, del.
• Hashmap storage hset, hget, hdel, hfields, hvalues.

IRN client abstraction is bound to the irn global state to be accessible from handlers.

The record TTL is 30 days. (Which should be ok for sessions).

How Has This Been Tested?

• Unit test for the helper function was implemented and run in CI.
• Test to run get, set, del were implemented. The test is ignored by default, because we don't want to spin up a cluster for each CI (and will be covered in the handler integration test).
  • It can be run locally by starting the local cluster and run cargo test -- storage::irn::tests::test_irn_client_set_get_del --exact --show-output --ignored. The test were successfully passed in the local environment.
• Test to run hashmap operations were implemented. The test is ignored by default, because we don't want to spin up a cluster for each CI (and will be covered in the handler integration test).
  • It can be run locally by starting the local cluster and run cargo test -- storage::irn::tests::test_irn_client_hashmap --exact --show-output --ignored. The test were successfully passed in the local environment.

Due Diligence

• [ ] Breaking change
• [ ] Requires a documentation update
• [ ] Requires a e2e/integration test update

[xDarksome]

The record TTL is 90 days. (Which should be ok for sessions).

does it need to be 90 days? our current longest living data is 30 days

I'm talking from the perspective of data migrations, if our highest value is going to be 90 days, then next time we decide to do full migration we would need to shadow the data for 90 days to be sure

And it probably will happen in the next 3 month, as we will be transitioning to the permissioned network

[geekbrother]

The record TTL is 90 days. (Which should be ok for sessions).

does it need to be 90 days? our current longest living data is 30 days

I'm talking from the perspective of data migrations, if our highest value is going to be 90 days, then next time we decide to do full migration we would need to shadow the data for 90 days to be sure

And it probably will happen in the next 3 month, as we will be transitioning to the permissioned network

It decreased to 30 days. The context: slack.