Introduce TCK AssertionId annotation

[scottmarlow]

Is your feature request related to a problem? Please describe.
The current TCK tests include @assertion_ids: in comments that identify which SPEC API (e.g. JAVADOC) or Specification document (e.g. JavaEE or Connector that I think should be replaced with a Java annotation that identifies similar information.

Describe the solution you'd like

Add a new assertion id annotation that includes:

1. link to the Specification section or JavaDoc description on jakarta.ee. A few example links: https://jakarta.ee/specifications/persistence/3.2/apidocs/jakarta.persistence/jakarta/persistence/entitymanager#clear() https://jakarta.ee/specifications/platform/11/jakarta-platform-spec-11.0-m5#a2009 (note milestone release link is fine which could be updated before final release of TCK).
2. description contains the current text of existing @test_Strategy but for new tests simply describes what the test is validating.
3. identifier unique id
4. tag can be used to identify test groups.

Additional context
http://docs.oasis-open.org/tag/guidelines/v1.0/cn02/guidelines-v1.0-cn02.pdf

[jamezp]

FWIW now that we use JUnit 5 this annotation could also be used, potentially at least, in the failure messages if a test fails.