fix: support type UUID from node's crypto package

[TheSalarKhan]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Using the UUID type from node's crypto package with the @nestjs/swagger plugin enabled crashes nestjs start npm run start with a cryptic error message.

Error: A circular dependency has been detected (property key: "id"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").

Example dto

import { UUID } from 'crypto';

export class CreateUserDto {
  name: string;

  id: UUID;
}

This problem goes away when the IsUUID() decorator from class-validator package is used. But considering the fact that UUID is an alias type UUID = `${string}-${string}-${string}-${string}-${string}`; the inferred type without any help should be string

Issue Number: N/A

What is the new behavior?

After this change, if the plugin is enabled, and no decorator is used on a property of type crypto.UUID then its type gets inferred as string in the openapi spec.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[kamilmysliwiec]

lgtm