fix(decorators): avoid setting type property on globals like String and Date

[vkarpov15]

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?

• [X ] 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?

@Prop(String) results in Nest setting String.type = String, which has caused some issues in Mongoose: Automattic/mongoose#11199, Automattic/mongoose#10807

Issue Number: N/A

What is the new behavior?

@Prop(String) treated as @Prop({ type: String })

Does this PR introduce a breaking change?

• Yes
• [X ] No

Other information

[micalevisk]

looks like you'll need to update this test as well:

mongoose/tests/e2e/schema-definitions.factory.spec.ts

Line 85 in a02d752

it('should generate a valid schema definition', () => {

[kirtan403]

When this be merged? We have upgraded our project from nest v7 to v8 and we are stuck because of this issue. We have a Location schema with type and coordinates keys and it throws validation failed: location.type: Cannot create property 'coordinates' on string 'Point'

@Schema()
export class Location {
  @Prop({ required: true, enum: ['Point'] })
  type: string

  @Prop({ type: [Number], required: true })
  coordinates: number[]
}

[kamilmysliwiec]

Tests are currently failing for this PR