* Revert mis-change, which makes the endpoint dependency breaking.

* Update change log.

* [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

* Only report `bug warning` in precise conditions.

* Add a test check for template existing.

* 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

Fix bug, the enhanced session could cache the metadata metrics(hot entity) forever. A new timeout mechanism is designed for avoiding this specific case.

Optimize this timeout mechanism, make it different for ES(one index per day) and non-ES storage implementation.

Adjust index refresh period as INT(flushInterval * 2/3), it used to be as same as bulk flush period. At the edge case, in low traffic(traffic < bulkActions in the whole period), there is a possible case, 2 period bulks are included in one index refresh rebuild operation, which could cause version conflicts. And this case can't be fixed through core/persistentPeriod as the bulk fresh is not controlled by the persistent timer anymore.

This PR should avoid the following exception in the low load case, especially when bulkActions is set larger than the number of a metric type.

* Performance: optimize IDs read of ElasticSearch storage options(6 and 7). Use the physical index rather than template alias name.

* 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>

Signed-off-by: NGao Hongtao <hanahmily@gmail.com>