replace InstrumentationLibrary with InstrumentationScope

[tsloughter]

Spec change can be found in PR:
open-telemetry/opentelemetry-specification#2276

[tsloughter]

This is mostly ready but need to find where it isn't backwards compatible and fix those spots.

I think the only place it isn't is that it would be getting rid of the instrumentation_library creation functions in opentelemetry module. I guess we just add those back and have them return scopes instead.

[codecov]

Codecov Report

Merging #405 (7dadcc2) into main (ccbe7f1) will decrease coverage by 0.04%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##             main     #405      +/-   ##
==========================================
- Coverage   73.23%   73.18%   -0.05%     
==========================================
  Files          53       53              
  Lines        1655     1656       +1     
==========================================
  Hits         1212     1212              
- Misses        443      444       +1     

Flag	Coverage Δ
api	68.59% <50.00%> (-0.12%)	⬇️
elixir	17.52% <0.00%> (-0.03%)	⬇️
erlang	74.60% <83.33%> (-0.05%)	⬇️
exporter	73.59% <85.71%> (ø)
sdk	78.09% <100.00%> (ø)
zipkin	53.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
apps/opentelemetry/src/otel_batch_processor.erl	70.10% <ø> (ø)
apps/opentelemetry/src/otel_simple_processor.erl	70.37% <ø> (ø)
apps/opentelemetry_api/src/opentelemetry.erl	80.00% <50.00%> (-0.90%)	⬇️
...ntelemetry_exporter/src/opentelemetry_exporter.erl	73.59% <85.71%> (ø)
apps/opentelemetry/src/otel_span_ets.erl	72.09% <100.00%> (ø)
apps/opentelemetry/src/otel_tracer_default.erl	100.00% <100.00%> (ø)
apps/opentelemetry/src/otel_tracer_server.erl	71.05% <100.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 ccbe7f1...7dadcc2. Read the comment docs.

[tsloughter]

Hmm, nevermind, it looks like we only have get_tracer/3 instead of a get_tracer that accepted an InstrumentationLibrary. So no user would be using opentelemetry:instrumentation_library. We may not want to bother keeping the function instrumentation_library in the module as it could be confusing and shouldn't be being used.

[ferd]

is it worth maintaining the type alias as well?

-type instrumentation_library() :: #instrumentation_scope{}. or something?

[tsloughter]

I doubt it. If any user actually uses the library record the least of what they have to deal with is the type spec.