docs: remove the lists of packages from the readme

[rauno56]

Which problem is this PR solving?

Every now and then we get a PR for updating the list in the Readme. I don't personally feel having a list in the readme is worth it if we can reference the folder the packages are all nested in but I'm also interested in what everyone else thinks.

Short description of the changes

1. Remove the lists of the included packages from the readme.
2. Reword some other parts about the support according to Discussion: Drop support for older Node.JS versions opentelemetry-js#2721 (comment)

[vmarchaud]

Apart from the lint failing, i agree that its a problem and the information is generally available elsewhere (specially in the opentelemtry website) so i'm in favor of removing them as-is and maybe replace them by a link to https://opentelemetry.io/registry/ ?

[dyladan]

I agree a link to the registry should be sufficient. I wonder if it would be possible to have a CI check that warns if the package is not in the registry?

[codecov]

Codecov Report

Merging #969 (0f28d5f) into main (b55b79b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #969   +/-   ##
=======================================
  Coverage   95.91%   95.91%           
=======================================
  Files          13       13           
  Lines         856      856           
  Branches      178      178           
=======================================
  Hits          821      821           
  Misses         35       35           

[rauno56]

Added a link to the registry.

I think linking straight to Registry in the main content of the readme creates weird UX(repo -> registry -> repo) with little benefit(registry search vs Ctrl-F).

I have a feeling that most people will arrive to the repo through npm anyway

[dyladan]

Added a link to the registry.

I think linking straight to Registry in the main content of the readme creates weird UX(repo -> registry -> repo) with little benefit(registry search vs Ctrl-F).

I have a feeling that most people will arrive to the repo through npm anyway

I think its fine how you did it. The registry links directly to packages though. Unless someone is already familiar with our package structure, they may find the registry easier to navigate. In any case this LGTM