Added integration test to reproduce #4099

[chkal]

This pull request contains a new integration test which reproduces #4099. Please see #4099 for a detailed description of the problem.

Steps to reproduce:

• Remove the @Ignored annotation in PriorityAnnotationOnExceptionMappersTest
• Run the test a few times
• You will see that the test randomly passes or fails

Setting a breakpoint here will show the root cause of the problem:

jersey/core-common/src/main/java/org/glassfish/jersey/internal/inject/Providers.java

Lines 363 to 371 in 895c293

	private static int getPriority(Class<?> serviceClass) {
	Priority annotation = serviceClass.getAnnotation(Priority.class);
	if (annotation != null) {
	return annotation.value();
	}
	// default priority
	return Priorities.USER;
	}

The method scans InstanceSupplierFactoryBridge instead of the actual implementation class for the @Priority annotation.

[chkal]

I updated the pull request and removed the @Ignore annotation on the test.

[alawrenc]

I know I'm coming in way too late, but doesn't this integration test demonstrate exactly the wrong behavior for exception mappers?
Per the jax-rs spec, post-request filters (including exception mappers by my understanding) are sorted in reverse order. https://docs.oracle.com/javaee/7/api/javax/ws/rs/Priorities.html
So a higher priority value should take precedence in this case