Provide the codebase of plugin tests. Make the plugin test in the CI loop.

* test: add service reset command test case

* test: update test case

* Exclude more generated sources and plugin instrumentation definition classes

* Support dynamically configure alarm settings

* Update documentation

* Provide Consul dynamic configuration center implementation

* Add more unit tests

* Fix unit test

* Add more unit tests and remove unused file

* Remove redundant doc

* Add tests on webapp to increase test coverage

* Rename test class

* Add tests on webapp to increase test coverage

* Fix unit tests

* Remove duplicated class

* Exclude generated sources from test coverage

* Exclude more generated sources

* Upgrade guava version to support higher JDK version

* Adjust license version

* Update doc

* Switch to SkyWalking CI nodes

* Switch E2E to SkyWalking CI nodes

* Identify CI container name

* Try to bring coverall test coverage comments back

* Remove suspicious rule

* Sync

* Try checkout submodule

* Update labeler.yml

* Update labeler.yml

* Update labeler.yml

* Update labeler.yml

* Rebase

* Remove jmh annotation processor

* Update README.md

* Replace with placeholder and remove Coverall badge in README

* Exclude generated classes from coverage analysis

Modify `hot` to `host`

* add powered-by.md

add xin.com

* update powered-by.md

add xin.com

* Add pulsar apm plugin.

* Fix check style

* Fix pulsar consumer component define.

* Add pulsar to component-libraries.yml

* Fix error interceptor class.

* Add pulsar to agent support list.

* Add Pulsar to ComponentsDefine and component-libraries.yml

* Move create entry span log of consumer from after method to before method

* Fix send callback issue when exception cause.

* Fix test issues

* Move pulsar plugin to optional plugins

* Add none messages tests for interceptor of producer and consumer.

* Remove unused comments.

* Move pulsar plugin back to the apm-sdk-plugin

* Fix comments

* remove set startTime for entry span(default is set by System.currentTimeMillis)

* Fix comments

* sync ui

* sync skywalking-query-protocol
sync ui

* sync skywalking-query-protocol

sync ui

* sync ui

* MOD: Compatible with KafkaTemplate

* MOD: modify test

* Exclude the test codes from source release.

* Don't depend on antd anyway.

* Committer vote and set up document.

* Change document link structure.

* Fix typo.

* Revert labeler

* Remove .travis.yml as well

Remove .travis.yml as well since it's disabled permanently

* sync ui

* query-server-time-info

* query-server-time-info

* query-server-time-info

* query-server-time-info

* query-server-time-info

* sync skywalking-query-protocol

* sync ui

* sync ui

* sync skywalking-query-protocol

* sync skywalking-query-protocol

* Polish labeler settings and support submodule

* Trigger labeler

* Add more labeler paths

* Bugfix: labeler not work

* Fix yaml file indent

* Try GitHub actions to automatically label pull requests

* Add more labels

* Add test label

* Support timeout configuration in agent and backend.

* Fix CI

* no message

* Update docker-entrypoint.sh

* Set telemtry instance id in etcd and nacos plugins

* Add feature to control the maximum history agent log files.

* Language of instance could be NULL

* Fix style check.

* Fix duplicated test cases.

* Add Light4J 1.6.x plug-in

* Add unit test for Light4J plug-in

* Add missing id to server-starter

* Remove mentions of version 1.6.x

Some local testing showed that the plugin successfully generated traces for a light4j project built with light-codegen v2.x. Therefore, there is no need for a separate plugin for v2.x and no distinction needs to be made with light4j v1.6.x.

* Update supported light4j versions

* Use ContextSnapshot to maintain trace

In a typical Light4j project, the ExceptionHandler#handleRequest is the asynchronous execution point. The flow is ExceptionHandler#handleRequest -> HttpServerExchange#dispatch -> ... -> ExceptionHandler#handleRequest. This means that handleRequest is being intercepted twice and each time a LocalSpan is created. Without handling thread propagation, the trace segment gets split up.

By saving a ContextSnapshot into the enhanced object (ExceptionHandler), we can determine if it is necessary to continue the segment.

* Update logic for span creation in trace

By default, the Light4J plugin now overrides the Undertow plugin's entry span with its own. This new entry span is created just before execution of the ExceptionHandler#handleRequest in the I/O thread. The entry span is generated here because it is considered the starting point of the Light4J handler chain.

There is now also the option to enable detailed span creation when tracing requests through Light4J. These local spans mark which middleware and business handlers are involved with handling the HTTP request to a Light4J service.

* Update skywalking version

* Update light4j version

* Fix LightInstrumentation javadoc

* Remove import violating checkstyle

This import was added from the link reference in the javadoc. The javadoc has now been changed to just reference the method name.

* Move light4j agent config property

* Sync UI

* agent support custom properties.