Bug: Migration from v2.8 to 4.x failed

[kbeaugrand]

Expected Behavior

When migrating from v2.x to v4.x, the application should migrate its data correctly.

Current Behavior

Migration of the application has failed. When migrating the device model commands, the following message appears:
MessageText: null value in column "Name" of relation "DeviceModelCommands" violates not-null constraint.

All tables in the storage account remain empty after the test and the portal is not operational until the models are reinserted into the database.

Steps to Reproduce

1. Install v2.x portal
2. create some LoRaWAN models
3. Migrate the portal to v4.x

Context (Environment)

Portal version: 4.11.0
LoRaWAN Stack version: N/A

Logs

2023-05-12T08:51:26.990449625Z An exception occurred in the database while saving changes for context type 'AzureIoTHub.Portal.Infrastructure.PortalDbContext'.
2023-05-12T08:51:26.991984038Z Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
2023-05-12T08:51:26.992006438Z ---> Npgsql.PostgresException (0x80004005): 23502: null value in column "Name" of relation "DeviceModelCommands" violates not-null constraint

Additional Information