Added Brave, OTel, Zipkin & Wavefront (#1)

* WIP on adding wavefront, brave, otel and zipkin

* Moved most of the code

* Added tests

* Added brave & otel local sample setup for zipkin

* Fixed setup

* Bumped libs

* Fixed javadoc issues

* Updated dependencies

* Added milestone & snapshot repo

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,9 +1,6 @@
 ---
-name: Bug report
-about: Report a bug in Micrometer Tracing
-title: ''
-labels: bug
-assignees: ''
+name: Bug report about: Report a bug in Micrometer Tracing title: ''
+labels: bug assignees: ''
 
 ---
 
@@ -12,9 +9,10 @@ A clear and concise description of what the bug is.
 
 **Environment**
 <!-- In what environment did the bug happen? -->
- - Micrometer Tracing version [e.g. 1.7.1]
- - OS: [e.g. macOS]
- - Java version: [e.g. output of `java -version`]
+
+- Micrometer Tracing version [e.g. 1.7.1]
+- OS: [e.g. macOS]
+- Java version: [e.g. output of `java -version`]
 
 **To Reproduce**
 How to reproduce the bug:

.github/ISSUE_TEMPLATE/enhancement-request.md

@@ -1,9 +1,6 @@
 ---
-name: Enhancement request
-about: Request an enhancement for Micrometer
-title: ''
-labels: enhancement
-assignees: ''
+name: Enhancement request about: Request an enhancement for Micrometer title: ''
+labels: enhancement assignees: ''
 
 ---
 

.github/workflows/gradle-wrapper-validation.yml

@@ -1,5 +1,5 @@
 name: "Validate Gradle Wrapper"
-on: [push, pull_request]
+on: [ push, pull_request ]
 
 jobs:
  validation:

CONTRIBUTING.md

@@ -2,33 +2,37 @@
 
 This Contributing Guide is intended for those that would like to contribute to Micrometer Tracing.
 
-If you would like to use any of the published Micrometer Tracing modules as a library in your project, you can instead include the Micrometer Tracing artifacts from the Maven Central repository using your build tool of choice.
+If you would like to use any of the published Micrometer Tracing modules as a library in your project, you can instead
+include the Micrometer Tracing artifacts from the Maven Central repository using your build tool of choice.
 
 ## Code of Conduct
 
 See [our Contributor Code of Conduct](https://github.com/micrometer-metrics/.github/blob/main/CODE_OF_CONDUCT.md).
 
 ## Contributions
 
-Contributions come in various forms and are not limited to code changes.
-The Micrometer Tracing community benefits from contributions in all forms.
+Contributions come in various forms and are not limited to code changes. The Micrometer Tracing community benefits from
+contributions in all forms.
+
+For example, those with Micrometer Tracing knowledge and experience can contribute by:
 
-For example, those with Micrometer Tracing knowledge and experience can contribute by: 
 * TODO: [Contributing documentation]()
 * Answering [Stackoverflow questions](https://stackoverflow.com/tags/micrometer-tracing)
 * Answering questions on the [Micrometer slack](https://slack.micrometer.io)
 * Share Micrometer Tracing knowledge in other ways (e.g. presentations, blogs)
 
-The remainder of this document will focus on guidance for contributing code changes. It will help contributors to build, modify, or test the Micrometer Tracing source code.
+The remainder of this document will focus on guidance for contributing code changes. It will help contributors to build,
+modify, or test the Micrometer Tracing source code.
 
 ## Contributor License Agreement
 
-Contributions in the form of source changes require that you fill out and submit the [Contributor License Agreement](https://cla.pivotal.io/sign/pivotal) if you have not done so previously.
+Contributions in the form of source changes require that you fill out and submit
+the [Contributor License Agreement](https://cla.pivotal.io/sign/pivotal) if you have not done so previously.
 
 ## Getting the source
 
-The Micrometer Tracing source code is hosted on GitHub at https://github.com/micrometer-metrics/tracing.
-You can use a Git client to clone the source code to your local machine.
+The Micrometer Tracing source code is hosted on GitHub at https://github.com/micrometer-metrics/tracing. You can use a
+Git client to clone the source code to your local machine.
 
 ## Building
 
@@ -50,8 +54,8 @@ The Gradle `check` task depends on the `test` task, and so tests will be run as
 
 ### Publishing local snapshots
 
-Run `./gradlew pTML` to publish a Maven-style snapshot to your Maven local repo.
-The build automatically calculates the "next" version for you when publishing snapshots.
+Run `./gradlew pTML` to publish a Maven-style snapshot to your Maven local repo. The build automatically calculates
+the "next" version for you when publishing snapshots.
 
 These local snapshots can be used in another project to test the changes. For example:
 

README.md

@@ -34,9 +34,9 @@ dependencies {
 
 ## Milestone releases
 
-Milestone releases are published to https://repo.spring.io/milestone.
-Include that as a maven repository in your build configuration to use milestone releases.
-Note that milestone releases are for testing purposes and are not intended for production use.
+Milestone releases are published to https://repo.spring.io/milestone. Include that as a maven repository in your build
+configuration to use milestone releases. Note that milestone releases are for testing purposes and are not intended for
+production use.
 
 ## Documentation