jersey-container-servlet-core-4.0.0M2 references ServiceFinderBinder from unexpected package in jersey-common

**Description:**

While testing an upgrade from jersey-container-servlet-core-3.1.11 to jersey-container-servlet-core-4.0.0-M2, I encountered what appears to be a package reference inconsistency involving `ServiceFinderBinder`.

### Observed behavior

WebComponent.java in `jersey-container-servlet-core-4.0.0-M2` attempts to load:

```java
org.glassfish.jersey.innate.inject.ServiceFinderBinder
```

However, the class is actually present in:

```java
org.glassfish.jersey.internal.ServiceFinderBinder
```

within `jersey-common-4.0.0-M2`.

### Comparison with jersey-container-servlet-core-3.1.11

* `jersey-container-servlet-core-3.1.11` references:

```java
org.glassfish.jersey.internal.ServiceFinderBinder
```
* `jersey-common-3.1.11` contains:

```java
org.glassfish.jersey.internal.ServiceFinderBinder
```

The reference and implementation locations are consistent.

### jersey-common-4.0.0

I verified that `ServiceFinderBinder` is still located in:

```java
org.glassfish.jersey.internal.ServiceFinderBinder
```

inside `jersey-common-4.0.0`.

However, `jersey-container-servlet-core-4.0.0-M2` appears to look for:

```java
org.glassfish.jersey.innate.inject.ServiceFinderBinder
```

which results in a runtime failure.

### Question

Is this an unintended package reference in `jersey-container-servlet-core-4.0.0-M2`?

If so, would it be possible to correct the reference in a future milestone/release?

I can provide stack traces, dependency information, and a minimal reproduction if needed.