🐛  user was not imported, but the importer tries to correct the reference (#8722)
🐛  user was not imported, but the importer tries to correct the reference (#8722)

no issue

- this is usually an edge case, but i investigated because i thought that the importer is broken
- the importer logic is build like this:
   - it creates a transaction
   - this transactions runs through:
      - beforeImport
      - doImport
      - afterImport
   - afterImport corrects user references and if a user could not be imported, we have to protect that
       NOTE: we could create two transactions to be more correct, but building this had no priority because of edge cases only
             having two transactions would solve: you first add the data (error or success), then you correct the data
   - usually a user can be always imported (!), but there are a few edge cases (e.g. multiple roles attached)
TryGhost/Ghost,Kikobeats/Ghost,JohnONolan/Ghost,leninhasda/Ghost,janvt/Ghost,sebgie/Ghost,kevinansfield/Ghost,Gargol/Ghost,mohanambati/Ghost,kevinansfield/Ghost,janvt/Ghost,ErisDS/Ghost,bitjson/Ghost,mohanambati/Ghost,cwonrails/Ghost,Gargol/Ghost,sebgie/Ghost,bitjson/Ghost,JohnONolan/Ghost,e10/Ghost,BlueHatbRit/Ghost,leninhasda/Ghost,kevinansfield/Ghost,BlueHatbRit/Ghost,ErisDS/Ghost,sebgie/Ghost,cwonrails/Ghost,mohanambati/Ghost,acburdine/Ghost,dbalders/Ghost,dbalders/Ghost,acburdine/Ghost,acburdine/Ghost,TryGhost/Ghost,e10/Ghost,Kikobeats/Ghost,TryGhost/Ghost,chevex/undoctrinate,dbalders/Ghost,ErisDS/Ghost,cwonrails/Ghost,Kikobeats/Ghost,JohnONolan/Ghost