Integrate go-build-tools crosslink

[bryan-aguilar]

Updates the crosslink target to reference the go.opentelemetry.io/build-tools/crosslink package found here.

I have also ran crosslink prune to remove all the extraneous replace statements. No make target was added for crosslink prune but if desired we could either add a new target for that or pass in the --prune flag so that a prune is executed on every run.

Fixes #1529

[codecov]

Codecov Report

Merging #2886 (f8af6c5) into main (c7cf945) will increase coverage by 0.0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #2886   +/-   ##
=====================================
  Coverage   75.7%   75.7%           
=====================================
  Files        177     177           
  Lines      11819   11819           
=====================================
+ Hits        8950    8954    +4     
+ Misses      2636    2632    -4     
  Partials     233     233           

Impacted Files	Coverage Δ
sdk/trace/batch_span_processor.go	82.1% <0.0%> (+1.8%)	⬆️

[pellared]

pass in the --prune flag so that a prune is executed on every run.

At first glance, it seems the most effective approach. Any downsides if we do that?

[bryan-aguilar]

At first glance, it seems the most effective approach. Any downsides if we do that?

There really isn't any in this context. While it's a destructive action the repository is already under version control so it's all completely reversible. Also, continually pruning would ensure that the go.mod files are kept clean. I would probably update the echo before the crosslink action is executed to provide more context so no one is surprised.