1.8.3-SNAPSHOT -> 1.8.3

1.8.2 -> 1.8.3-SNAPSHOT

1.8.2-SNAPSHOT -> 1.8.2

Agents running in container often have meaningless agent ids, so sorting them by agent ids do not have merit.
Sorting them by their start timestamp (in descending order) would be more useful.

MySQL java connector's PreparedStatement execute methods move around a lot by versions and may produce unnecessary NotFoundInstrumentException logs.

For example, MySQL java connector 6.x have both PreparedStatement and ServerPreparedStatement classes, with the execute methods in PreparedStatement.
MySQL java connector 8.0.11+ only have ServerPreparedStatement class, with the execute methods in it.
To cover both cases, execute method interceptors need to be added to both of these classes, which will result in NotFoundInstrumentException log when running MySQL java connector 6.x.

(cherry picked from commit 97687f49)

Consumer traces would occasonally arrive before producer traces resulting in test failures.
Change so that consumer traces and producer traces are checked separately while still checking for trace ordering within them.

- Dispatch the latest data when either the period or the end-time has changed
- No need to check if the period has changed in each component because the store always has the latest state

- Refactor the update path logic