feat: replace uuid dependency with native crypto method

[backflip]

About this Pull Request

• What kind of change does this PR introduce?
  • Replace external uuid-random dependency with native crypto.randomUUID. No need to use external code for something the platform provides.
• What is the current behavior?
  • Usage of external dependency.
• What is the new behavior?
  • Usage of native functionality.
• Does this PR introduce a breaking change?
  • As crypto.randomUUID has been introduced with Node.js 16.7.0 and the engine config in this project's package.json states "node": "18 || 20 || >=22.0.0", this should not break anything.
• Other information:
  • FWIW, runtimes like Deno support this approach, too. And current versions of every major browser. So portability should not be affected. Rather the opposite.
  • When this feature was implemented, there was no native solution available yet.

Pull Request Checklist

• My code follows the code style of this project
  • Run npm run lint to double check
• My change requires a change to the documentation
  • I have updated the documentation accordingly
• I have added tests to cover my changes
  • Run npm run test to run the unit tests and npm run coverage to generate a coverage report
• All new and existing tests passed
• My commit messages follow the commit guidelines

[sebbo2002]

I've still counter-checked this as I didn't have the removal of random-uuid on my mind until the deprecation of node.js v18. But you are absolutely right, it came earlier than I thought. Thank you very much.

[sebbo2002]

🎉 This PR is included in version 8.1.0-develop.1 🎉

The release is available on:

• npm package (@next dist-tag)
• JSR.io
• GitHub release
• v8.1.0-develop.1

Your semantic-release bot 📦🚀

[sebbo2002]

🎉 This PR is included in version 8.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• JSR.io
• GitHub release
• v8.1.0

Your semantic-release bot 📦🚀