let's get config from zos-config instead of hard coded values

[ashraffouda]

currently we have alot of config managed from environment.go like chainurls, activation urls ....
it is better if we kept those values as default if we didn't find values in zos-config and depend on zos config instead which will keeps changes to min when urls changed/added or removed wihtout changing everytime in codebase

[Eslam-Nawara]

WIP

• updated config.go and environment.go to have all configuration from zos-config
• removed all hardcoded urls and updated the node to get urls from zos-config
• updated registrar module to reload config on every registration retry
• working on updating the node so that if config changes with time, it restarts the services depending on the updated config.

[Eslam-Nawara]

WIP

• now all urls are fully configurable from zos-config
• I think we need to continue working on restarting the modules with changes to config in a new pr as this one has many changes
• need to discuss with ashraf the changes we need to do to be able to update the node urls if the config changed while the node is running.

[Eslam-Nawara]

wip

• updated substrate gateway to be able to update the open connection used by the module
• updated zos-api module so we can update the service if any of substrate url or relay url changed

[Eslam-Nawara]

work completed,

• updated zosbase to load config from zos-config on demand
• updated zos module api-gateway and noded to monitor changes in sub urls and relay urls and update modules if needed

[Eslam-Nawara]

updated the pr threefoldtech/zos_base#33 with the newest changes to main and added back the multiple []hub URLs and testing the node features

Note: this expects hub URLs to be []string not only string

deploying VM:

and the VM is accessible

Node logs:

zui

[Eslam-Nawara]

Updated 3 pr to the latest on main and was able to boot a node with the new changes

• I'm able to deploy a VM on it after booting, and before updating any config

• It will only update substrate connections at runtime if the current connection is broken and zos-config is updated with new health URLs

• it updates the rmb peer if the relay is updated

• trying to deploy a VM after the relay URLs are updated

• and I'm able to access the VM normally