Browser detector module

[Abinet18]

Which problem is this PR solving?

Adds a browser detector module to get browser identification attributes like platform, brands, mobile, language and add it to the resource attributes of the traces. Improvement of the same purpose PR(#3201) that modifies the detector in @opentelemetry/resources. Since the resources was a stable package , we agreed on creating a new experimental package for the browser detector.

Short description of the changes

Added a new experimental package @opentelemetry/opentelemetry-browser-detector , added BrowserDetector module that queries for navigator.userAgentData if supported or just navigator.userAgent and returns the resulting resource object

Type of change

Please delete options that are not relevant.

• [ x] New feature (non-breaking change which adds functionality)
• [ x ] This change requires a documentation update

How Has This Been Tested?

• Unit test written
• importing this module and checking the traces contain the browser attributes in the resource span

Checklist:

• [ x ] Followed the style guidelines of this project
• [ x ] Unit tests have been added
• Documentation has been updated

[Abinet18]

@legendecas , can you look into this when you get some time

[legendecas]

@Abinet18 Sorry for the delay, I'm on vacation this week. I will take a look at this when I'm back. Thank you for your work on this!

[legendecas]

Thank you for working on this! Overall LGTM % a few nits.

[codecov]

Codecov Report

Merging #3292 (ef9fbac) into main (a3e40da) will decrease coverage by 0.65%.
The diff coverage is 18.51%.

❗ Current head ef9fbac differs from pull request most recent head fae5ec4. Consider uploading reports for the commit fae5ec4 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3292      +/-   ##
==========================================
- Coverage   93.52%   92.87%   -0.66%     
==========================================
  Files         244      231      -13     
  Lines        7386     6677     -709     
  Branches     1529     1386     -143     
==========================================
- Hits         6908     6201     -707     
+ Misses        478      476       -2     

Impacted Files	Coverage Δ
...ntelemetry-browser-detector/src/BrowserDetector.ts	15.38% <15.38%> (ø)
...ckages/opentelemetry-browser-detector/src/types.ts	100.00% <100.00%> (ø)
api/karma.worker.js	0.00% <0.00%> (-100.00%)	⬇️
packages/opentelemetry-resources/karma.worker.js	0.00% <0.00%> (-100.00%)	⬇️
...kages/opentelemetry-sdk-trace-base/karma.worker.js	0.00% <0.00%> (-100.00%)	⬇️
...lemetry-resources/src/detectors/BrowserDetector.ts	53.33% <0.00%> (-46.67%)	⬇️
...lemetry-resources/src/detectors/ProcessDetector.ts	95.45% <0.00%> (-4.55%)	⬇️
...-sdk-trace-web/src/enums/PerformanceTimingNames.ts
...-instrumentation-fetch/src/enums/AttributeNames.ts
...ation-xml-http-request/src/enums/AttributeNames.ts
... and 13 more

[legendecas]

LGTM

[MSNev]

LGTM, if you can just address the lint and changelog check failures we should be good

[Abinet18]

@dyladan Is there something I can do to fix the failing checks ?

[legendecas]

@Abinet18 You can run npm run update-ts-references at the root of the project to update TS project references to ensure the compilation order. Also, in order to run the browser tests, https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-resources/package.json#L25 need to be configured.

Or I can help to set up the miscellaneous configurations for the browser testing and releases, if you are ok with it.

[Abinet18]

@legendecas , I am ok if you setup the required configs.

[legendecas]

Updated with browser testing and fixed lerna package linking issues.

[legendecas]

@dyladan @MSNev would you mind taking another look? thank you!

[MSNev]

@dyladan LGTM