Sample prototype HealthCheck API changes

[sst...@redhat.com]

There are two sample prototypes for the API changes raised in issue 43, and further discussed in:

https://groups.google.com/forum/#!topic/microprofile/8l8AEmaduJ0

https://groups.google.com/forum/#!topic/microprofile/zaLWMqFp7HA

The pull requests:

https://github.com/eclipse/microprofile-health/pull/59

https://github.com/eclipse/microprofile-health/pull/60

I see John has raised another API usage issue regarding the name(String) in the response build and response named(String) static method.

[John D. Ament]

It looks like the only difference between the two is the use of "builder" vs "named" as the property.

My concern with name is that it shouldn't be part of the response object, but instead some how derived from the check (for instance, Metrics HealthChecks are registered with their names - http://metrics.dropwizard.io/3.1.0/manual/healthchecks/ ).  However, if we need to keep it we should leave it as "named" since it's clearer what its for.

So my vote would be for #60

[Heiko Braun]

John, please vote on the github issues themselves. This makes it easier for us to track the responses.

[Heiko Braun]

The github (thumbs up/down) feature is pretty useful at counting votes automatically.

[Heiko Braun]

We've discussed both proposals on todays call and based on the information available to the participants (github votes, ML comments) decided to move forward with PR #60.  Across all the comments we collected, there seem to be minor issues with each approach, but overall #60 seem to be the preferred one. Please don't see this a negative if #59 was your preference, but more as an invitation to iterate with us on the code base (read: your PR's are welcome).