Add support for more data type

[Aryan1296]

Feat: Add Support for Custom and Enum Data Types

This pull request resolves issue #1 by introducing robust support for user-defined custom data types, including PostgreSQL ENUMs. This enhancement empowers users to model their databases with greater accuracy and flexibility, accommodating a much wider range of data types directly within the DrawDB interface.

Problem

Previously, DrawDB was limited to a predefined list of data types. This was a significant constraint for users who rely on powerful PostgreSQL features like enumerated types (ENUM) or specialized types provided by extensions (e.g., ULID). The inability to specify these types meant that database diagrams were often incomplete or required manual workarounds, complicating the development process.

Solution

Instead of adding new types on a case-by-case basis, this implementation adds a dynamic, user-driven solution. Users can now add custom data types directly within the column's user interface.

This approach provides two key benefits:

Immediate Support for ENUMs: Users can now define columns with ENUM types as they would in a standard PostgreSQL schema.

Future-Proof Flexibility: The platform can now handle any custom data type from PostgreSQL plugins or user-defined types without needing further updates from the DrawDB team.

Key Changes:
Enhanced UI: The "Data Type" field in the column editor now allows for free-text input, enabling users to specify any custom type.

Schema Accuracy: The generated diagrams and scripts will now correctly reflect the use of ENUMs and other custom types.

Improved Developer Workflow: Eliminates the need for workarounds and ensures that the visual model in DrawDB is a true representation of the database schema.