fix!: standardize supported versions and set upper bound limit

[blumamir]

This PR is not breaking any existing behavior, it only aligns everywhere to use a consistent versioning syntax and documentation, as well as capping supportedVersions for any existing instrumentation

• make sure there is upper limit on all supported versions so that they do not attempt to patch a new major version
• align the range to a common format. It seems many instrumentation where using >=x.y.z <w writing so I used it
• README.md: added where missing, moved to always be after Installation section, added package name and npm link before version range to give more context.
• added section to GUIDELINES.md
• replace all the use of astrix * for unordered list style in makrdown to use dash -, it causes errors in markdown linter after introducing new sections.

related: open-telemetry/opentelemetry-js#4693
related: open-telemetry/opentelemetry-js#4696

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: blumamir / name: Amir Blum (7b0e95d, 47713dd, e5ca81b, 93e2961, d5a4290, b354455, 9d76835, 857fea3, bb8c2bb, f2cb90d, 622a97c, 1ac55f1, 8455d96, c188978, 4e31da4, 0c7a463, b84dbf3, 5e66cff, 9d269ae, 548b8c4, 87f84dd, 1602d53, 47cdc01, b2bafbe, af9d138, 7186912, 6a367bf, 831c32d, fdd6a19, 8405555, eecf73f, fb4815e, 79f4fe8, c94ea20, eba1e0d, 3abf5af, 096f5c5, 7f71c9a, 8582727, f471dff, 0d238c3, 5b5375a, 0c07a5c, 684f719, 89eb937, 3402f50, 96638c2, 88ab4fa, fa20292, 22a8139, 35ab033, 3dff4b5, ea5718a, 314f302, cf866e1, fc98fcd, 1d02804, cb72c24, aaca52d, 7eacab4, 4168fea, e02a7c3)

[blumamir]

@trentm @JamieDanielson I think I addressed all the comments from your reviews. Since these are a lot of changes, please have a look again. I think EasyCLA is having hard time with the commits done via the code suggestion feature of PR comments in the UI. I will squash and merge all the commits after your review so to not lose and existing comments.

The one last thing I am not sure about is if we should choose caret ^ range when the version range is just one major version. I am split on this, but tend to prefer replacing it with >=1.0.0 <2 instead of ^1.0.0. WDYT?

Thanks again for those great comments suggestions and catches.

[trentm]

Some nits. I think it would be good to not have this labelled as purely a "docs" PR because it does include code changes for a few modules to add an upper limit on the instrumented versions.

[JamieDanielson]

The one last thing I am not sure about is if we should choose caret ^ range when the version range is just one major version. I am split on this, but tend to prefer replacing it with >=1.0.0 <2 instead of ^1.0.0. WDYT?

I actually prefer >=1.0.0 <2 over ^1.0.0 and would support using that. It also makes it more consistent with the other larger ranges.

[JamieDanielson]

/easycla

[trentm]

I actually prefer >=1.0.0 <2 over ^1.0.0

Same.

[JamieDanielson]

I have similar nits to what Trent pointed out, aside from those LGTM 👍

[blumamir]

The one last thing I am not sure about is if we should choose caret ^ range when the version range is just one major version. I am split on this, but tend to prefer replacing it with >=1.0.0 <2 instead of ^1.0.0. WDYT?

I actually prefer >=1.0.0 <2 over ^1.0.0 and would support using that. It also makes it more consistent with the other larger ranges.

Changed the caret as described 👍

[blumamir]

Addressed all the comments (I think). @JamieDanielson @trentm can you please have one last look so this can merge? thanks again for the great feedback