Block server start until origins file is loaded.

[mikkokar]

Problem Description:

YamlFileConfigurationService doesn't prevent Styx HTTP server from starting if it doesn't successfully load an initial origins configuration file.

Therefore, Styx server starts without sensible origins configuration. All requests to its HTTP port will return 404 NOT FOUND, with message Not found: pathPrefixRouter in response body.

This affects only the new YamlFileConfigurationService. The old monolithic application router is unaffected.

Root Cause & The Fix

Problem was caused by ServiceProviderMonitor which loads all service providers from Yaml providers block. It didn't wait for the underlying service providers to be started correctly.

I fixed this by modifying the ServiceProviderMonitor class so that it waits for all underlying services to successfully start up before declaring itself as healthy to phase1 service manager.