Do a more robust check that peer_id does not correspond to the CENTRAL_CONTENT_BASE_INSTANCE_ID.

[rtibbles]

Summary

• Some backend code assumed that peer_id = None was the way to express that Studio was being connected to, this assumption is now false
• Updates this to compare to the precomputed CENTRAL_CONTENT_BASE_INSTANCE_ID

References

Fixes issues observed during testing of #11083

Reviewer guidance

Does importing with hotfixes set as the CENTRAL_CONTENT_BASE_URL work.

N.B. this will not fix an issue that will still arise if a Studio instance is added as a StaticNetworkLocation.

---

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.0b1.dev0_git.98.gcdec2a02.pex
Windows Installer (EXE)	kolibri-0.16.0b1.dev0+git.98.gcdec2a02-unsigned.exe
Debian Package	kolibri_0.16.0b1.dev0+git.98.gcdec2a02-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.16.0b1.dev0+git.98.gcdec2a02-0.3.0.dmg
TAR file	kolibri-0.16.0b1.dev0+git.98.gcdec2a02.tar.gz
WHL file	kolibri-0.16.0b1.dev0+git.98.gcdec2a02-py2.py3-none-any.whl

[rtibbles]

Test failure is now fixed on release branch.

[bjester]

Confirmed this fixes the behavior I experienced.

[bjester]

Test failure is now fixed on release branch.

Merging noting this