chore: remove lerna

[david-luna]

Which problem is this PR solving?

This is a follow up PR of #2493. It removes lerna as a dependency and also from the CI workflows. All scripts and lerna commands have been replaced by its equivalent in nx (lerna was using them internally) or custom scripts.

Changes

• remove unnecessary scripts in packages (precompile & prewatch)
• remove lerna dependency
• update scripts/peer-api-check.mjs to work at the root level and the dependant workflows
• add publish-to-npm.mjs script and update the release workflow
• added a focus npm script for people who does not want to compile all project to start developing
• added scripts/bump-package-versions.mjs to help with manual releases
• update docs

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.80%. Comparing base (162feb1) to head (60400f0).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2526      +/-   ##
==========================================
+ Coverage   90.75%   90.80%   +0.04%     
==========================================
  Files         169      169              
  Lines        8018     8018              
  Branches     1632     1632              
==========================================
+ Hits         7277     7281       +4     
+ Misses        741      737       -4     

see 1 file with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[david-luna]

note to reviewer: although nx documentation says using folder names is okay I found this option to be more sensitive to changes.

[david-luna]

note for reviewer: this script was used only here so now it's changed to walk over all packages to do the API check.

[david-luna]

note for reviewer: necessary dependency for the next step

[david-luna]

note to reviewer: IMO this step was missing since npm publish will pack and publish the packages in whatever state it is. With a full compilation everything should be in the right state for publishing

[david-luna]

note to self: although manual release is unlikely to happen we should provide a way to do it. So we need to provide an alternative to the command lerna publish --skip-npm --no-git-tag-version --no-push

Do not merge this PR until this is resolved.

[david-luna]

This is now implemented in ./scripts/bump-package-versions.mjs

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.