* Fix sort metrics failured in H2 storage

* Fix postgre DB

The ES persistence execution is now asynchronous and the execution
latency only counts the time to insert the requests into the bulk
processor, instead of the time after the requests are flushed into the
storage, this patch fixes that issue.

There is the same issue in prepare latency but that needs more changes
so I'll leave it to another pull request.

* [maven-release-plugin] prepare release v8.8.0

* [maven-release-plugin] prepare for next development iteration

* Create changes-8.8.0.md

* Reset changelog for 8.9.0

* Fix H2EventQueryDAO doesn't sort data by Event.START_TIME.

* Fix H2EventQueryDAO uses a wrong pagination query.

DataCarrier changes a `#consume` API to add properties as a parameter to initialize consumer (#7452)

* Remove page path in the browser log query condition.

* Remove endpoint name in the backend log query condition.

* [Break Change] Remove endpoint name in the trace query condition.

* Fix a local UT error(MacOS only)

* [maven-release-plugin] prepare release v8.7.0

* [maven-release-plugin] prepare for next development iteration

* Performance: remove the synchronous persistence mechanism from batch ElasticSearch DAO. Because the current enhanced persistent session mechanism, don't require the data queryable immediately after the insert and update anymore.
* Performance: share `flushInterval` setting for both metrics and record data, due to `synchronous persistence mechanism` removed. Record flush interval used to be hardcoded as 10s.
* Remove `syncBulkActions` in ElasticSearch storage option.
* Increase the default bulkActions(env, SW_STORAGE_ES_BULK_ACTIONS) to 5000(from 1000).
* Increase the flush interval of ElasticSearch indices to 15s(from 10s)

Add these 2 references. According to these, **(same _index, _type and _id) in same bulk will be in order**
1. https://github.com/elastic/elasticsearch/issues/50199
2. https://discuss.elastic.co/t/order-of--bulk-request-operations/98124

Notice, the order of different bulks is not guaranteed by the ElasticSearch cluster. We are going to have the risk of dirty write. But consider we set over 20s period between flush, and index flush period is 10, we should be safe.

Recommend 5000 bulk size and 15s flush interval only. The persistent period has been set to 25s.

* OAL supports generating metrics from events

* Add new dashboard for event metrics

* Add some docs for event metrics

Co-authored-by: Nkezhenxu94 <kezhenxu94@apache.org>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

Support multiple implementations of StorageBuilder in different storage implementations - stage 2 (#6336)

Support multiple implementations of StorageBuilder in different storage implementations - stage 1. (#6334)

* [maven-release-plugin] prepare release v8.4.0

* [maven-release-plugin] prepare for next development iteration