Proposal: optional utility types (Password, EmailAddress, DSN, etc.)

[rnag]

I’m considering whether it makes sense for dataclass-wizard to ship a small set
of optional utility types (value objects) that are commonly useful when
loading/serializing data.

Examples (illustrative, not final):

• Password – masks value in repr / print, but allows explicit access
• EmailAddress – parses/normalizes email strings
• RedisDsn / PostgresDsn / Dsn – structured DSN parsing (similar to Pydantic)

These would:

• behave like thin wrappers around strings
• integrate cleanly with existing type hooks
• remain fully optional (no heavy validation framework)

Questions:

• Are these kinds of types useful to you in practice?
• Which ones would you actually want?
• Should these live in core, or in an optional submodule (e.g. dataclass_wizard.types)?

Looking for feedback before deciding on scope or API.