…3051)

Motivation:

It can be very difficult to know if a thread is slow or completely
stuck without taking multiple thread dumps and comparing them.

Modifications:

Try to mitigate this by saving the time stamp of the last blocking
`.get()` call. This should then show up in heap dumps and we can
at least compare them to see if they've all started blocking at
about the same time or if there is a big spread. The latter would
suggest they are truly stuck.

Motivation:

Gradle interprets `*.module` files differently than the `pom.xml`.
Because every module currently depends on `servicetalk-dependencies`,
users pulled its `dependencyConstraints` in their build configurations
with any servicetalk module as transitive dependency and got unintended
changes for other dependencies.

For example, `servicetalk-annotations` that has only jsr305 as a 3-party
dependency still forces upgrade of jackson, protobuf, log4j, netty, and
jersey for users because it depends on `servicetalk-dependencies`.

Modifications:

- Remove `servicetalk-dependencies` from every module, instead define
every necessary dependency by its version number or import only
required boms;
- Update `servicetalk-dependencies` to include missed dependencies:
opentelemetry, instrumentation, resilience4j;
- Correct dependencies for all `-jersery3` modules to keep only what
they use;
- Move all `platform` dependencies from the top to their corresponding
scope;
- Regenerate lock files;

Result:

Users don't get unintended dependency upgrades because of the `*.module`
file handling.

Motivation:

It's exposed on `@ElementsAreNonnullByDefault` and therefore should be
an `api` dependency instead of `implementation`. It will also help us
to avoid adding `com.google.code.findbugs:jsr305` dependency for every
module that already adds `servicetalk-annotations`.

Modifications:

- Change `api` to `implementation` for `com.google.code.findbugs:jsr305`
in `servicetalk-annotations`;
- Remove `com.google.code.findbugs:jsr305` from every module that
already adds `servicetalk-annotations`;
- Regenerate lock files;

…or (#3057)

Motivation:

There is a perf regression in the DefaultLB in compatibility mode compared to
the round-robin LB when under very high request rate and that is at least in part
attributable to lock contention for the health indicator EWMA.

Modifications:

Don't create a health indicator if the EWMA half life is 0.

Motivation:
HttpRequestMetaData#hasQueryParameter(String) returns false when there is
a query parameter with no value. This is incorrect and it should return true.

Motivation:
041f3dc replace empty string for
null during parsing. However the setter/accessor methods don't
consistently allow null values.

Modifications:
- Allow null values from add & set queryParameter methods.