add multiconfig for launch workers

[BillyWooo]

as the title.
Launch workers with [local parachain / staging parachain / production parachain]

resolves #1000

[codecov-commenter]

Codecov Report

Merging #1056 (f7b0ea6) into dev (8b7f31b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1056   +/-   ##
=======================================
  Coverage   20.70%   20.70%           
=======================================
  Files         217      217           
  Lines        9013     9013           
=======================================
  Hits         1866     1866           
  Misses       7147     7147           

Impacted Files	Coverage Δ
...tentry/core/data-providers/src/twitter_official.rs	0.00% <ø> (ø)
tee-worker/service/src/main.rs	0.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[Kailai-Wang]

Overall it looks better, thanks.

The biggest concern is still what should be defined in dev/staging/prod configs -- I'll forward this to @jingleizhang

[Kailai-Wang]

I think staging is the conventional word 😂, same for worker_config_*

[BillyWooo]

🤣

[Kailai-Wang]

when shall we run launch.sh and when launch.py?

[BillyWooo]

Both are fine. launch.sh would be more preferred for local launch & test. launch.py + config.json would have more flexibility on ports parameter inputs (launch.sh will just increase the port number between different worker. config.json can give any port number).

[Kailai-Wang]

I think -u and -m can be confusing/conflicting: can I use -u wss://parachain-eu-0.staging.litentry.io and -m dev at the same time? Again it depends what are dev/staging/prod supposed to do

[BillyWooo]

I think there is no shortcut for 'running-mode'. Always need to type the full name. I also feel confusing about these parameter shortcuts. That's the reason NO shortcut provided here.

[Kailai-Wang]

I don't see a difference between dev/staging/prod, this needs a clear definition: what exactly should differ in these different configs? -- needs to be evaluated/defined by who opens this issue (maybe @jingleizhang)

[BillyWooo]

Yes. For the moment. These three files are almost dummy placeholders. Need to define/clarify later.

[jingleizhang]

At least we have those prod/staging/dev config files so that we can work with the same application code in different environments.

All parameters should be moved into the config file, and only one parameter that represents the env needs to be kept, actually. But for now, we're just using the config to save some no-more hard-coded information. At least it helps us keep some api keys safe.

Please correct me if I'm wrong: prod stands for Litentry, staging means parachain-eu-0.staging.litentry.io, and dev means rococo.

I think we could change those names to something more clear if we think it's necessary. 😂