Add additional checks and enforcement around Deprecation to the build system. [LUCENE-5719]

It would be great if we enforced a reasonable minimum for deprecation use.

Something like:

- Both the annotation and the comment should be required.
- Comment deprecation should require a comment.
- Annotation should require a JIRA url. (Doesn't seem we could do this nicely :( )

I run into, and perhaps even write, too many places with Deprecate and no helpful path or clue for the user and obviously Deprecation should be as non confusing as possible and polite deprecation enforced to the degree that we can do it.

---
Migrated from [LUCENE-5719](https://issues.apache.org/jira/browse/LUCENE-5719) by Mark Miller (@markrmiller)

The issue names no files, tests, or build entry points. Start by locating Lucene's existing deprecation checks and enforcement in the build system, then determine which of the proposed requirements are feasible. Done means the agreed deprecation rules are enforced and covered by appropriate build tests.

Written by the indexing model from the issue text.