Convert fetch plugin to instrumentation

[obecny]

Which problem is this PR solving?

• Fixes Convert fetch plugin to instrumentation #1655

Short description of the changes

• Convert fetch plugin to instrumentation
• Updated to use semantic conventions to avoid duplicates from local attributes definitions (HttpAttribute)

[codecov]

Codecov Report

Merging #1796 (6ae8908) into master (4ab9465) will decrease coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1796      +/-   ##
==========================================
- Coverage   92.49%   92.10%   -0.39%     
==========================================
  Files         173      159      -14     
  Lines        6019     5169     -850     
  Branches     1287     1110     -177     
==========================================
- Hits         5567     4761     -806     
+ Misses        452      408      -44     

Impacted Files	Coverage Δ
...ry-exporter-collector/src/CollectorExporterBase.ts
...lemetry-exporter-collector/src/transformMetrics.ts
...mentation-xml-http-request/src/enums/EventNames.ts
.../opentelemetry-exporter-collector/src/transform.ts
...emetry-instrumentation-xml-http-request/src/xhr.ts
...ackages/opentelemetry-web/src/WebTracerProvider.ts
...ntelemetry-web/src/enums/PerformanceTimingNames.ts
...kages/opentelemetry-exporter-collector/src/util.ts
packages/opentelemetry-web/src/utils.ts
packages/opentelemetry-web/src/types.ts
... and 2 more

[dyladan]

I thought we agreed to keep both plugin and instr until the new loader was ready?

[obecny]

I thought we agreed to keep both plugin and instr until the new loader was ready?

for node yes, for web it is fully compatible it will have just a different name, see XMLHTTPRequest it is the same

[dyladan]

Looks great thanks