v2.0.0

!!! Breaking Changes !!!

The beeline will no longer propagate dataset configuration across distributed traces. To ensure distributed traces continue to send data to the appropriate dataset either:

1. [Recommended] Configure a dataset in every instrumented application (e.g. using the honeycomb.beeline.dataset property). Most users configure their applications this way already, so you may not need to do anything.
2. Alternatively, configure a custom trace propagation hook to inject dataset in the outgoing request header, and a custom trace parser hook to extract dataset from the incoming request header.

Enhancements

• Add support for Environment & Services (#187) | @MikeGoldsmith
• add service.name field in addition to service_name (#188) | @JamieDanielson
• fix: only trim service name for dataset (#189) | @JamieDanielson

Maintenance

• Bump maven-jxr-plugin from 2.5 to 3.1.1 (#126) | dependabot
• gh: add re-triage workflow (#174) | @vreynolds
• Bump mockito-core from 4.1.0 to 4.2.0 (#177) | dependabot
• update releasing.md for current temporary issue (#178) | @JamieDanielson
• update maven orb to handle multi-module project (#179) | @JamieDanielson
• merge releases-1.x.x into main (#193) | @vreynolds