The migration 20210622 breaks the flows by declaring the wrong hostid for the interfaces

The hostids used before and after the migration are not the same, which breaks the existing flows by introducing new and non-existant partner names.

For example, a partner with type R66 are setup to use a hostid and a hostidssl ({hostid}-sll by default). Before the migration, hostid and hostid-ssl are used to create the accesses in the partners they exchange files with. After the migration, hostid-local_server-1-r66 and hostid-local_server-1-r66-ssl are used (resp.), but it does not match the reality, which is that this R66 partner will authenticate itself as hostid or hostid-ssl, and its authent will be rejected.

The previously used conventions should be used in the migration in order to ensure a continuity of service.