Fix publishing jaeger-thrift shadow artifact

[zhalas]

Which problem is this PR solving?

• Missing shadow artifact ([jaeger-thrift] Shadow artifact went missing #645)

Short description of the changes

• add publication and signing configuration for jaeger-thrift shadow artifact (this is currently not published as the current configuration only publishes components.java + sources + javadocs)

Testing performed

• ./gradlew publishToMavenLocal -PskipSigning=true and verified that the shadow artifact is deployed to local maven repository
• ./gradlew publishToMavenLocal and observed that :jaeger-thrift:signShadowPublication fails (it's not a full test, but should be good enough)

[codecov]

Codecov Report

Merging #704 into master will increase coverage by 0.18%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #704      +/-   ##
============================================
+ Coverage     89.57%   89.76%   +0.18%     
- Complexity      587      588       +1     
============================================
  Files            70       70              
  Lines          2159     2159              
  Branches        282      282              
============================================
+ Hits           1934     1938       +4     
+ Misses          136      132       -4     
  Partials         89       89              

Impacted Files	Coverage Δ	Complexity Δ
...ing/internal/samplers/RemoteControlledSampler.java	91.25% <0.00%> (-1.25%)	16.00% <0.00%> (-1.00%)
...gertracing/internal/reporters/LoggingReporter.java	90.90% <0.00%> (+9.09%)	5.00% <0.00%> (+1.00%)
...rtracing/internal/reporters/CompositeReporter.java	100.00% <0.00%> (+28.57%)	7.00% <0.00%> (+1.00%)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b50aa15...9e7a319. Read the comment docs.

[yurishkuro]

@pavolloffay you're more familiar with this setup, can you review?

[yurishkuro]

@zhalas could you describe how you tested this? Unfortunately out CI will only test the release process when doing the actual release.

[zhalas]

@yurishkuro I described my testing in Testing performed section in the PR description. The test was to publish to local Maven repository. I haven't fully tested the signing part (see the mentioned section), but if you want I can do that as well.

[yurishkuro]

Thanks!

[yurishkuro]

@zhalas getting failures when publishing to Sonatype:

Invalid POM: /io/jaegertracing/jaeger-thrift/1.3.0/jaeger-thrift-1.3.0.pom: Project name missing, Project description missing, Project URL missing, License information missing, SCM URL missing, Developer information missing

#722

[zhalas]

@yurishkuro I will look on Monday.