hardcode data provider config into prod enclave

[kziemianek]

• Removes running-mode CLI arg
• Hardcodes data provider config for prod env
• Adds reading secrets from env variables
• Adds possibility for overriding data provider config by env variables on non prod env
• Decouples data providers from global config variable (configs are provided as constructor parameters)
• StfTaskContext holds reference to ShieldingKeyRepository because shielding key can be changed after mu-ra key provisioning.

[linear]

P-233 Hardcode the data provider URL/constants into prod enclave

As topic - currently these configurations (e.g. "official_twitter_url", achainable endpoint etc) are read from the file. This is risky as the enclave operator could use a wrong config file intentionally or unintentionally, it also means they are free to change the endpoint.

Basically we need to:

• for prod: hardcode these constants (including the discord role ids maybe?) to enclave logic
• for dev: allow to override the constants by reading from file

[BillyWooo]

In general, the refactor looks good for me. Let's get the CI tests pass.
Two concerns:

1. how does this refactor affect the mock server?
2. I would suggest to wait for PRs from @zhouhuitian and @higherordertech and merge after theirs PRs merged. Because this refactor will block their deployment to current staging env.

[kziemianek]

@BillyWooo this PR doesn't affect mock server. Regarding waiting for other PRs im fine with it. We can wait even longer - untill we drop staging branch.

[Kailai-Wang]

Looks good, thanks!

[BillyWooo]

untill we drop staging branch.

I would say so. Thanks

[0xverin]

@BillyWooo this PR doesn't affect mock server. Regarding waiting for other PRs im fine with it. We can wait even longer - untill we drop staging branch.

Will we affect the mock server in the future?

[kziemianek]

@BillyWooo this PR doesn't affect mock server. Regarding waiting for other PRs im fine with it. We can wait even longer - untill we drop staging branch.

Will we affect the mock server in the future?

I think we don't have any plans for it.
We can adjust mocks logic to fit our testing needs.

[kziemianek]

I've made few changes, there very plenty of conflicts and problem with shielding key so I'm requesting a review again 🙃

[BillyWooo]

in general, LGTM. Some points to talk with you privately.

[BillyWooo]

Please resolve the conflict and get CI jobs pass. Thank you.