Summary

• Adds database upgrade 2025101501 that completes the removal of the role_level column from tbl_role_permissions
• Migration 2025092004 was supposed to drop this column, but the ALTER TABLE was wrapped in a try/catch that silently swallowed failures
• On upgrades from older versions (e.g. r14xx), the column survives as NOT NULL without a default, and the old unique key stays on (role_level, permission) instead of (role_id, permission)

This causes:

SQLSTATE[HY000]: General error: 1364
Field 'role_level' doesn't have a default value

when saving role permissions, since the application code only inserts (role_id, permission, granted).

What the upgrade does

1. Checks if role_level column still exists (idempotent — no-op if already removed)
2. Ensures role_id column exists and migrates data if needed
3. Removes orphan rows where role_id is NULL
4. Deduplicates (role_id, permission) rows
5. Drops all indexes that reference role_level
6. Drops the role_level column (re-throws on failure — this must succeed)
7. Ensures the correct unique key exists on (role_id, permission)

Test plan

• Fresh install: upgrade runs without errors (column doesn't exist, early return)
• Upgrade from r14xx with leftover role_level: column is dropped, permissions work
• Upgrade from recent version where 2025092004 already succeeded: idempotent no-op

Fixes #1527