Bug: Migration from v4.13 to v5.x doesn't work

[Metal-Mighty]

Expected Behavior

Migration should apply changes required to move from an existing v4.13 database to a v5.x database

Current Behavior

Migrations are applied but the portal doesn't work properly when it's done

Steps to Reproduce

1. Install the portal in v4.13
2. Insert data in models, devices, etc.
3. Deploy version v5.x connected to the same database

Context (Environment)

Portal version: 4.13 -> 5.x
LoRaWAN Stack version: N/A

Logs

Additional Information

[judramos]

In database, there is a column job_class_name in quartz table job details.
As projects has been renamed in v5, there are errors when quartz jobs try to start.