feat: generate id field using uuid

[rodrigodosanjosoliveira]

Fixes #158

Proposed Changes

1. Replace uuid package with the native Node.js crypto module:

• Removed the dependency on uuid package from package.json.
• Updated all UUID generation to use the native randomUUID() function from the Node.js crypto module.

2. Update Migration Generation for UUID Handling:

• Improved migration generation logic to handle UUID columns appropriately based on the database.
• For PostgreSQL, the id field is generated using uuid_generate_v4() as the default value for primary keys.

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• Remember to check if code coverage decreases, if so, please implement the necessary tests

Reviewing Maintainer

• Label as breaking if this is a large fundamental change
• Label as either automation, bug, documentation, enhancement, infrastructure, or performance

[codecov]

Codecov Report

Merging #191 (d137937) into main (1099e97) will not change coverage.
The diff coverage is n/a.

❗ Current head d137937 differs from pull request most recent head 6fd4b18. Consider uploading reports for the commit 6fd4b18 to get more accurate results

@@           Coverage Diff           @@
##             main     #191   +/-   ##
=======================================
  Coverage   68.75%   68.75%           
=======================================
  Files          28       28           
  Lines         560      560           
=======================================
  Hits          385      385           
  Misses        175      175           

Impacted Files	Coverage Δ
src/generators/src/packagejson.js	100.00% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dalssoft]

Thanks @rodrigodosanjosoliveira for the contribution

[dalssoft]

On the migrations you would need something like this:
table.uuid('id').primary().defaultTo(knex.raw('uuid_generate_v4()')) (Postgress)
where this line could change for each DB supported (PG, SQL Server, MySQL, etc)

[rodrigodosanjosoliveira]

@dalssoft
I updated the migration generation logic to handle UUID columns according to the database. For Postgres, it now uses uuid_generate_v4() as the default value for UUID primary keys. Thanks for pointing this out!