Migrate texera database from mysql to postgres

[shengquan-ni]

Overall Direction

This pull request removes all MySQL dependencies and transitions the Texera platform to rely on PostgreSQL.

Key Code Changes

Type Changes

1. org.jooq.types.UInteger was replaced with scala Integer.
2. TINYINT(1) columns (often used as booleans in MySQL) changed to proper BOOLEAN columns.
3. Status fields switched from Byte to Short or Enum-based values based on the jooq code generation.

Updated jOOQ

1. Regenerated all classes under dao/jooq/generated to reflect the new PostgreSQL schema.
2. Upgraded jOOQ library from 3.14.16 to 3.16.6 to include bug fixes on generated SQL queries.
3. Upgraded jOOQ codegen from 3.12.4 to 3.16.10 to include bug fixes on generating DAO files.

Query Adjustments

1. Rewrote queries that previously used MySQL-specific syntax in fulltext-search.
2. Revised a few raw SQL strings to jOOQ queries for better maintainability.

MockDB changes

1. Mock DB now uses an embedded Postgres DB.

Migration Guide

1. before pulling the latest master, backup your workflows and datasets by downloading them if necessary.
2. pull the latest master and refresh sbt project to load the updated sql packages.
3. install postgres database (version > 14) on your local dev environment.
4. use psql -U postgres to log in to postgres. If psql command is not found and you are using Mac OS, follow this answer to fix the issue.
5. run \i /path/to/texera_ddl.sql to initialize the texera DB.
6. enable the user system on both backend and frontend, then create a user for yourself.
7. re-upload your dataset and workflow if needed.

[kunwp1]

LGTM! Left some minor comments.

[aglinxinyuan]

LGTM!

Tested on my local machine.