Support for multiple HealthChecks that resolve to a single health check status

The current Karyon and Eureka health check implementation attempts to consolidate multiple health states into a single status in a way that uses unwieldy dependencies between various conditions for health check.  This PR provides a generic solution through which multiple HealthCheck components may be registered and resolved into a single strategy using a plugable strategy.  

Several new concepts are introduced here,
1.  HealthCheck that when invoked returns a Status object
2.  The Status object tracks a single isReady boolean as well as an error.  The combination of these two variables yields 3 states.  
   (isReady=false, error=null)  Component is initializing
   (isReady=false, error=nonnull) Component failed to initialize 
   (isReady=true, error=null) Component has been initialized and is working properly
3.  HealthCheckRegistry through which multiple HealthCheck conditions may be registered.  The default implementation takes multibound Set<HealthCheck> as well as the existing karyon HealthCheckHandler as well as a HealthCheck based on the manual status tracked by ApplicationInfoManager.
4.  HealthCheckInvoker strategy for invoking the actual health checks.  A basic inline implementation is provided.  A more robust implementation will include parallelizing the health checks and adding timeouts.
5.  EureakHealthCheckResolver strategy for resolving the health checks into a single Eureka status. 

Note that this implementation depends on a (yet to be issued) update to eureka where ApplicationInfoManager tracks an InstanceStatus separately instead of setting that status directly on the singleton InstanceInfo.  This solves various race conditions whereby the InstanceInfo status can be updated independently outside of the context of healthcheck.

An example use case for this mechanism is to track an application's healthcheck using 3 conditions.
1.  Karyon server initialization which is set after Guice returns
2.  HealthCheckHandler
3.  ApplicationInfoManager.setInstanceStatus being manually set.

All 3 conditions must be set to a healthy status for an InstanceInfo.UP status to be set on the eureka client
Since we are moving away from single boolean, why not introduce a more complete service status model with { Starting, PartiallyReady, Ready, Down, Error } states?

There is different semantic associated with each:
* Starting - some time in the future I will be ready
* PartiallyReady - I am providing limited service, possibly due to problem with communicating with backend services
* Read - complete set of services provided
* Down - state after service/library shutdown call was made
* Error - any other error condition (with associated cause)