feat(flex): Ensure Deterministic Column Ordering in jansPerson / gluuPerson Schema Across Installations

**Summary**

Column ordering in the jansPerson (formerly gluuPerson) table is inconsistent across Flex + PostgreSQL installations. For example, the "profile" attribute may appear as column 4 in one environment and column 24 in another. Although queries are by name, one of our enterprise customers relies on fixed column positions for downstream ingestion pipelines.

**Problem**

Schema generation does not enforce a consistent column order.

Result: each installation may produce different ordinal positions.

This causes issues for customers using strict schema validation (Kafka, ETL, etc.).

**Expected Behaviour**

New installations should always generate the jansPerson table with the same, deterministic column ordering, regardless of environment.