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

[flevi29]

Pull Request

What does this PR do

• switches package manager to npm
• updates and shortens GitHub actions regarding the setup of Node.js with the help of composite 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 99.17%. Comparing base (b74efe8) to head (6e41796).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1899      +/-   ##
==========================================
+ Coverage   98.53%   99.17%   +0.63%     
==========================================
  Files          16       16              
  Lines        1574     1574              
  Branches      343      348       +5     
==========================================
+ Hits         1551     1561      +10     
+ Misses         23       13      -10     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Strift]

This looks good to me. Although, I prefer merging this after we're done with the v1.14 release.

Happy to merge the ts-eslint changes before though. Is there any reason for grouping them in this PR?

[flevi29]

@Strift I'll separate it. npm gave peer dependency errors, I had to update it, that's why I grouped it.

[flevi29]

@Strift #1900