refactor(ci): Updated the publish command in the CI to use npm publish instead of lerna publish

[sdangol]

Summary

This PR updates the make-release and publish-package Github workflows to switch from using publish commands from lerna to the native npm publish command to publish the packages to the npm registry.

Changes

• Updated the lerna publish command to npm publish in the make-release.yml and publish-package.yml Github workflows
• For generating provenance statements, the --provenance flag was used
• The from-package from lerna was removed as npm publish uses the --workspaces flag to publish all the workspaces which are not marked as private. If a package with the same version is tried to be published, it will throw an error
• To publish an individual package through publish-package.yml, the --workspace <workspace-path> was used

Issue number:
#4171

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dreamorosi]

Thank you for the work on this PR and for the tests in the issue!

We can address this either in this PR or in the PR we'll open for #4170, but in L72 of the make-release workflow we're reading the version number from the lerna.json file, which will be removed/no longer updated.

To replace that line I'd consider reading the version from packages/commons/package.json since it'll always be updated.

[sdangol]

Yeah, let's do that in the PR that we open next which probably would remove all the lerna dependencies as well.

[github-actions]

@aws-powertools/lambda-typescript No related issues found. Please ensure 'pending-release' label is applied before releasing.