jersey-spring should respect @Profile annotations

During registration of all jersey resource bindings, the jersey spring integration should make sure to exclude any component for which the proper profile is not active.
This should be both on class and method level.

Current behaviour will just (try to) create a bean behind your back anyway using the Injections abstraction.
In some cases this will fail, because the required dependencies are not (and should not be) available because of the inactive profile.

Expected behaviour:
Any rest endpoint with an @Profile annotation that points to an inactive profile should not be available and thus respond with a 404 if the jersey-spring extension is active.
#### Affected Versions
[2.26-b02]

Start by locating jersey-spring's registration of Jersey resource bindings and how it handles Spring @Profile annotations at class and method level. Reproduce the inactive-profile case described in the issue, then verify that the endpoint is not created and responds with 404 when the jersey-spring extension is active.

Written by the indexing model from the issue text.