docs: [Browser] Define the support browser runtimes #4168

[MSNev]

As part of v2 preparation and defining the based supported set of browser / runtimes.

While defined as a v2 Issue, there is no readme for v2, so adding to core

Issue: #4168 [Browser] Define the support browser runtimes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.27%. Comparing base (f8ab559) to head (b6789fc).
Report is 30 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5032      +/-   ##
==========================================
- Coverage   93.39%   93.27%   -0.13%     
==========================================
  Files          46      317     +271     
  Lines         712     8194    +7482     
  Branches      120     1640    +1520     
==========================================
+ Hits          665     7643    +6978     
- Misses         47      551     +504     

see 266 files with indirect coverage changes

[t2t2]

Not sure if w3schools is the most professional place to link to, not expecting something as thick as the spec but maybe caniuse since MDN doesn't have an equivalent page?

[MSNev]

@dyladan, @pichlermarc Does OpenTelemetry have a specific (official / semi-official) site that we should use for externally referencing language references?

[pichlermarc]

@MSNev I'm not aware of any guidelines regarding that - I think we should use a link to the spec as there's no way to misunderstand what we're talking about. If there's a need for additional links we can still add them later on.

[pichlermarc]

Looks good already, thanks @MSNev 🙂

As you mentioned in the SIG meeting last week, we currently don't have a way to deal with README.md changes for the next branch.

I think rather than merging it into main where this is immediately visible we should create a file on the next branch called README_NEXT.md. Then, when we're ready to release 2.0 we will create a PR to manually merge the README.md from main with README_NEXT.md to get the final output (I'll create an issue so that we don't forget). Since we manually merge the files later, the README_NEXT.md can just contain the browser support statement for now.

[pichlermarc]

@MSNev I'm not aware of any guidelines regarding that - I think we should use a link to the spec as there's no way to misunderstand what we're talking about. If there's a need for additional links we can still add them later on.

[MSNev]

Moving to next branch and renaming as suggested

[MSNev]

replaced by #5059