Switch from yarn to pnpm, improve workflows, add provenance to published package

[flevi29]

Pull Request

Related issue

Fixes #1660

What does this PR do

• switches package manager to pnpm
• updates and shortens GitHub actions regarding the setup of Node.js with the help of composite actions
  • https://pnpm.io/continuous-integration#github-actions
  • https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-composite-action
• adds provenance to published package
  • https://docs.npmjs.com/generating-provenance-statements
  • https://github.blog/security/supply-chain-security/introducing-npm-package-provenance/
  • https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages#publishing-packages-to-the-npm-registry

PR checklist

Please check if your PR fulfills the following requirements:

• Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
• Have you read the contributing guidelines?
• Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.84%. Comparing base (f3e4dd9) to head (4270d15).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1863   +/-   ##
=======================================
  Coverage   98.84%   98.84%           
=======================================
  Files          17       17           
  Lines        1565     1565           
  Branches      338      338           
=======================================
  Hits         1547     1547           
  Misses         18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[flevi29]

"Tests" workflow has a lot of repeating checkouts and builds, this bothers me but it looks like there's no simple solution to this, for whatever reason.
actions/checkout#19

[Strift]

"Tests" workflow has a lot of repeating checkouts and builds, this bothers me but it looks like there's no simple solution to this, for whatever reason.

Maybe in the future we could optimize by using something like nx.