Use crypto.randomUUID() instead of uuid module

[nikeee]

The crypto global is available in all supported Node.js versions as well as in all major browsers. The uuid module is rendered unnecessary for uuidv4.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[pquerner]

As far as I can see the package uuid priorities the native crypto module if its available. So I would leave this as is.

[nikeee]

The main motivation behind this PR was to reduce traffic in the realms of e18e. firebaes-admin has around 1466130 downloads per week. So requiring a 3.7 kB package results in 5.5GB/week, which is approx. 286 GB per year.
The crypto object isn't loaded by default in Node.js 18 (could be solved by using require("crypto").webcrypto), which is still supported until end of April. So according to the package.json's engine, this would be a breaking change. Maybe someone can do it some day.