Add an 'is-in-service' health check wrapping rabbit:is_serving/0 (backport #13872)

[mergify]

Proposed Changes

This is useful for a load balancer, for example, to be able to avoid sending new connections to a node which is running and has listeners bound to TCP ports but is being drained for maintenance.

This PR covers the first part of #13782: adding a new health-check GET /api/health/checks/is-in-service.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes issue #NNNN)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause an observable behavior change in existing systems)
• Documentation improvements (corrections, new content, etc)
• Cosmetic change (whitespace, formatting, etc)
• Build system and/or CI

Checklist

Put an x in the boxes that apply.
You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally with my changes
• If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
• If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

  ---

  This is an automatic backport of pull request Add an 'is-in-service' health check wrapping rabbit:is_serving/0 #13872 done by Mergify.

[michaelklishin]

@the-mikedavis please don't forget to set the milestone when merging :)