fix: Rewrite the vfolder status migration in #1892

[achimnol]

The migration in #1892 requires a manual alembic stamp command after running the alembic upgrade command. This will break many developers and fieldops members.

This PR migrates the vfolders.status enum column to a VARCHAR(64) column to avoid complex enum value substitution and simplify the migration process.

• fix: Rewrite the vfolder status migration (7ff52ff68bfc_detail_vfolder_deletion_status.py)
  • Remove errorneous commit during alembic migration scripts
  • Use jsonb functions to convert the key names in the status_history column at once
• refactor: Add models.base.StrEnumType for stringified enum columns

Warning

If your ./py -m alembic current says 7ff52ff68bfc, you must downgrade the existing migration first BEFORE applying this PR's commit with a manual stamping afterwards,
and then upgrade again AFTER applying this PR's commit (no longer manual stamping required).

git pull  # checkout the main branch after this PR is merged
git checkout 29e940b659e61410d0007de1cd30691b65929cf7  # the parent commit of this PR's merge commit
./py -m alembic downgrade a5319bfc7d7c
./py -m alembic stamp a5319bfc7d7c
git checkout main
./py -m alembic upgrade head

If you haven't applied the PR commit f5a8bbf from #1892, you may just simply run the upgrade.
(i.e., when your ./py -m alembic current does NOT say 7ff52ff68bfc, just git pull && ./py -m alembic upgrade head)

Checklist: (if applicable)

• Milestone metadata specifying the target backport version
• Mention to the original issue