Handle case when username doesn't exist on remote and try to create it.

[rtibbles]

Summary

• Adds extra exception handling to handle case where the username does not exist on the remote

References

Fixes #12191

Reviewer guidance

Follow the steps in the issue above ^

---

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.16.2b2.dev0_git.7.g40dd0695.pex
Windows Installer (EXE)	kolibri-0.16.2b2.dev0+git.7.g40dd0695-windows-setup-unsigned.exe
Debian Package	kolibri_0.16.2b2.dev0+git.7.g40dd0695-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.16.2b2.dev0+git.7.g40dd0695-0.4.2.dmg
Android Package (APK)	kolibri-0.16.2b2.dev0+git.7.g40dd0695-0.1.3-debug.apk
TAR file	kolibri-0.16.2b2.dev0+git.7.g40dd0695.tar.gz
WHL file	kolibri-0.16.2b2.dev0+git.7.g40dd0695-py2.py3-none-any.whl

[pcenov]

Hi @rtibbles - I confirm that the issue described in #12191 is fixed now. I've also regression tested the other migration scenarios without finding any other issues.