* Update elasticsearch client 7.0.0 to elasticsearch client 7.5.0.
* Update CHANGES.md and LICENSE.

The cancel steps were tried in separate jobs but it causes
an unnecessary increase in the number of jobs blocking the queue
even if we limited parallelism. This PR combines all the cancel
actions into a single job with multiple steps.

While this is a bit more copy&pasting and less DRY it is also
far more optimised and "aggressive" - i.e. once any cancel
job starts to be running it will immediately cancel all duplicates
for all workflows.

Instead of multiple workflow-runs generated for different workflows
this change replces it with single workflow, cancelling all others.
It is triggered by only one CI-IT workflow, because this one is
always triggered when all others are. It also sets parallelism
of the matrix to 4, so that there are not too many jobs in
parallel taken when this workflow runs.

* Add FAQ about VNode on the UI.
Co-authored-by: Nkezhenxu94 <kezhenxu94@apache.org>

* Polish the context and optimize the tag analyze

* Fix bug of new context codes.

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

* 1.Add ThreadPoolExecutor for handle kafka message.
Co-authored-by: NDaming <zteny@foxmail.com>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

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

* add oal excludes and includes to support tags
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

* add http client parameter collector
* Update CHANGES.md
Co-authored-by: Nkezhenxu94 <kezhenxu94@apache.org>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

Co-authored-by: NMrproliu <mrproliu@lagou.com>

* Make the duration error message more specific

The current implementation of envoy ALS K8S analysis is based on the hierarchy, pod -> StatefulSet -> deployment, StatefulSet, or others. It's freaky and different from the Istio Kubernetes registry.

The new path is pod -> endpoint -> service, and we should leverage Informer API instead of raw Kubernetes API.

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

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