Clean up users table by removing deprecated columns

[PG-Momik]

With the introduction of SSO, certain columns in the users table are now redundant. The application's database should closely mirror the user data schema provided by the IDP, maintaining only minimal additional fields required for app-specific logic.

Example:
Remove password
Remove registration_method

[emmajclegg]

Hi @PG-Momik - I'm assuming you'll be making these user database changes for the dev instance of IATI Publisher, which is completely separate to production? If so, go ahead.

We (ODS) are currently only interested in the production site user database, as we'll be using this to write an SQL migration script to import IATI Publisher users into our new CRM. This script will rely on the structure of the production user database staying the same between now and 1st Dec. I know @robredpath has requested a more recent snapshot of that database today.

To make you aware - we'll be requesting another copy of the production site user database at the start of our Registry migration week (i.e. 1st December). ODS will run our SQL migration script on that final snapshot, which will result in all IATI Publisher users registered up until the end of November getting migrated to our CRM. We will warn users of a period of IATI Publisher downtime that week, which will give YI time to switch IATI Publisher over to the new single sign-on and Register Your Data API set-up.

I hope that makes sense - any questions, let me know.

(cc'ing @james @chrisarridge for reference)

[PG-Momik]

@emmajclegg,

That's correct. For now, these database changes will be applied to the dev instance only.

We will not make any changes to the production database schema before December 1st, as requested. The production schema will only be updated to align with the new CRM structure during the planned downtime, after your team has completed the user migration.

cc: @BibhaT

[PG-Momik]

Dependencies:

Work on this is blocked by and should only begin after the successful completion of the following initiatives:

• Single Sign-On (SSO) Implementation
• "Register Your Data" API Changes

Critical Pre-Deployment Requirement:

Warning

Before commencing any development or deployment for #1871, a manual database backup is mandatory.

Rationale

While our DigitalOcean environment provides 7-day point-in-time recovery, this is a limited timeframe. A manual backup ensures an immediate and reliable restore point, mitigating risk during this specific implementation.