Implementation for Number data types

[kgodey]

Problem

Users will want to store numeric data in columns. We should allow them to do so and implement this type appropriately in the backend.

Proposed solution

We should support Number types in Mathesar and allow users to use them.

Tasks that need to completed:

• Design for Number data types #238
• Handle NUMERIC data type in the backend. #377
• Handle SMALLINT data type in the backend. #378
• Handle INTEGER data type in the backend. #379
• Handle BIGINT data type in the backend. #380
• Handle DECIMAL data type in the backend. #381
• Handle REAL data type in the backend. #382
• Handle DOUBLE PRECISION data type in the backend. #383
• Backend work for custom MATHESAR_TYPES.PERCENTAGE type. #434
• Implement filtering options for Number types. #385
• Implement range based grouping for numeric types. #384
• Implement display options for Number types. #386
• Frontend implementation of Number Mathesar type #258

Additional context

Related issues:

• Mapping DB data types to Mathesar data types #269
• Controlled casting #127
• Infer column type two #135

[mathemancer]

I think we should split out a separate issue for NUMERIC types with arguments to support the "decimal" type with specified decimal points, etc.

I also think we should split out different issues for each underlying DB type:

• REAL
• DOUBLE PRECISION
• SMALLINT
• INTEGER
• BIGINT

We should also have a separate issue for the percentage type¸ since that will require a custom type at the DB level, unlike the other types called for.

[kgodey]

@mathemancer I've split up the issues. I asked you a question on #386.

[kgodey]

Closing this since all subtasks are done.