This bundle packages OkHttp 4.12.x and *used to* add a class on top that simplified 
using (authenticated) HTTP proxies with OkHttp. This class still lives in
```
org.knime.okhttp3.OkHttpProxyAuthenticator
```
but now in `org.knime.okhttp3.fragment`. For now, re-packaging stays to simplify dependencies. 

Apart from packaging "annotations", "okhttp", and "okio" JARs, it additionally 
re-exports `org.jetbrains.kotlin.osgi-bundle` from the TP. Reason is that any 
interaction with Kotlin classes or types from OkHttp might sneakily throw 
NoClassDefFoundErrors at runtime, as Kotlin is invisible. This is a safety net.

---

The Eclipse IDE may not reliably resolve classes contributed by the `org.knime.okhttp3.fragment`
fragment for this host, even with `Eclipse-ExtensibleAPI: true`. Two solutions:

* Add to `.classpath` file in consuming plugins (current solution):
  ```
  <classpathentry kind="src" path="/org.knime.okhttp3.fragment"/>
  ```
  Then, open the fragment project in the workspace. This consistently resolves
  the `OkHttpProxyAuthenticator` class.

* Add to `.classpath` file in consuming plugins (alternative):
  ```
  <classpathentry kind="var" path="ECLIPSE_HOME/plugins/org.knime.okhttp3.fragment_5.12.0.QUALIFIER.jar"/>
  ```
  Immediately resolves the classes, but requires manual updates of the `QUALIFIER`,
  e.g. setting to "v202603300722" on fragment change.

We currently opt for the workspace reference (1st solution), instead of the TP reference.
