Support JAX-RS Annotation Inheritance

[tylerbenson]

This pull request add support for jax-rs annotations on a parent class or interface.

1. ByteBuddy ElementMatcher
hasSuperMethod is a new ElementMatcher that matches on a method or its definitions in any superclass or interface. This allows ByteBuddy to match a JAX-RS annotation on an implemented interface or superclass rather than just the concrete class. The performance impact should be minimal because the TypeMatcher for the instrumentation has to match first anyway. The TypeMatcher is unchanged.

2. A class hierarchy iterator
A deterministic iterator that walks a class's supertypes and implemented interfaces in a breadth-first manner.

3. Resource naming using the iterator
In JaxRsAnnotationsDecorator, we use the iterator to find the @Path annotation on the class as well as the relevant @Path and HttpMethod annotations on the method.

4. Updated Tests
Some new tests were added and previous tests updated to account for annotations at different levels of the hierarchy. Some old tests were incorrect in that they didn't account for annotation inheritance. Additionally, the commented-out tests that relied on Java 8 were manually checked to ensure no regressions versus #1061

[dougqh]

Looks good to me.

I think we're likely to optimize the matching process later.
But for now, JAX-RS supports inheritance in its semantics, so I think we should, too.

[devinsba]

There is definitely room for optimization (not traversing the tree excessively) but I don't see anything that should block getting this into users hands.

[devinsba]

Might be good to reference where in jax-rs this precedence order can be found since presumably this follows that implementation