* Bump up gRPC/protobuf to fix CVE-2021-2256

Support Apache IoTDB as a storage option, mostly refer to previous InfluxDB storage option.
* The Design of Apache IoTDB Storage Option, https://skywalking.apache.org/blog/2021-11-23-design-of-iotdb-storage-option/

Upgrade to the latest grpc-java 1.42.1 which is only compatible and [tested against](https://github.com/grpc/grpc-java/pull/8551#discussion_r714182190) 3.17.2, but we can assume that 3.17.3 (which has osx-aarch_64 compatible maven artifacts) is save to use.

We could have also upgrade to the latest grpc-java 1.42.1 and latest protoc 3.19.1, but it can not be directly done, it needs to tweak the grpcs-java internal dependencies. So we choose the safest option and discarded this option because of the following reasons:
 - Protoc 3.19.1 generates code that relies on methods not available in protobuf-java 3.17.2 ([“issue”](https://github.com/protocolbuffers/protobuf/issues/9236#issue-1059594027)) (which java-grpc relies on). So we need to tell grpc-java via dependency management to use 3.19.1 instead of 3.17.2.
Signed-off-by: NMarc Navarro Sonnenfeld <marcnavarro@tetrate.io>

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

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

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

Groovy naturally supports many dynamic features that we don't benefit for now but cost performance loss, in this patch we compile our Groovy-based DSL scripts statically to optimize performance.

* Introduce trivy to scan images
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

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

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

* Remove log4j 1.x
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Update CHANGES.md
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Update LICENSE refer to webapp
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

Add some defensive codes for NPE and bump up Kubernetes client version to expose exception stack trace (#6327)

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

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

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

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

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