Simply the service start process

We are still passing global parameters and the finality provider list into the service as required configuration for starting up the API service.

However, this is no longer necessary since we no longer publish new versions of the global parameters. Instead, we can hardcode the global parameters and finality provider list for all environments within the service and use an environment config value to select the appropriate set.

This approach will simplify the build process and service startup script. Since our service is also hosted by others, this change will make deployment more convenient.

Start with the API service startup script and its configuration path to identify where global parameters and the finality provider list are currently passed in. Trace the environment selection flow; done means each environment's values are selected from service configuration and startup no longer requires those lists as parameters.

Written by the indexing model from the issue text.