Work related to test failure in AvailabilityProxyConcurrencyTest
- Two changes to AvailabilityProxy itself
  - make AvailabilityProxy.getAvailability() a synchronized method. We don't
    want two threads calling this concurrently. This is not too likely
    in production, given intervals between checks, but may have been possible
    when performing a live check. The test code on the other hand was
    sometimes failing due to parallel execution of the call.
  - stop AvailabilityProxy.getAvailability() from converting UNKNOWN to
    DOWN when the avail check is asynchronously in progress.  This breaks the
    contract as stated in the javadoc and could lead to false DOWN reporting.
    (although, conversely, now fixed it could take longer for valid DOWN to
    be reported, as a check may need to timeout).
- unrelated but update AvailabilityFacet javadoc to add in valid MISSING state
om>
- work on the test code. replace the concurrent thread approach with the more
  realistic serialized calls and change timing around to more predictably
  mix some calls that complete synchronously and some that complete
  asynchronously.