refactor: remove uuid dependency and use native crypto.randomUUID

[LeonardoTonizza]

Description

This PR removes the external uuid dependency and replaces it with Node.js native crypto.randomUUID() for UUID generation.

Motivation

Since PR #2756 updated the minimum Node.js version requirement to v18, and crypto.randomUUID() has been available since Node.js v14.17.0, there is no longer a need for the external uuid package dependency.

Changes

• Removed uuid package from package.json
• Replaced import { v4 as uuid } from 'uuid' with import { randomUUID } from 'crypto'
• Updated all uuidv4() calls to randomUUID()
• Updated tests to use the native implementation

Testing

• [x] Existing unit tests pass

References

• Node.js crypto.randomUUID() documentation: https://nodejs.org/api/crypto.html#cryptorandomuuidoptions
• PR #2756

[gemini-code-assist[bot]]

Summary of Changes

Hello @LeonardoTonizza, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the project's dependency management by migrating from the third-party uuid library to Node.js's native crypto.randomUUID() for generating UUIDs. This change is enabled by a recent update to the minimum Node.js version requirement (v18), which ensures the availability of the native function. The refactor reduces the project's external footprint, potentially enhancing security and simplifying the build process by removing an unnecessary dependency.

Highlights

• Dependency Removal: The external uuid package and its corresponding @types/uuid dependency have been completely removed from the project's package.json and package-lock.json.
• Native UUID Generation: All instances of UUID generation now utilize Node.js's native crypto.randomUUID() function, leveraging built-in capabilities available since Node.js v14.17.0.
• Codebase Updates: Imports and function calls across relevant source and test files have been updated to reflect the switch from the uuid package to the native crypto module.
• Documentation Alignment: An internal documentation comment in src/eventarc/eventarc-client-internal.ts was updated to accurately describe the new method of UUID generation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.