Move core channel state into coach - the only place it is still used.

[rtibbles]

Summary

• Moves core channel state into the coach pluginModule

References

Fixes #12557

Reviewer guidance

Does the minimal fix to move the channel fetching logic from the core vuex state into coach.
Will presumably be cleaned up in the future by other changes.

---

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

• 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.17.0a0.dev0_git.211.g703f3654.pex
Windows Installer (EXE)	kolibri-0.17.0a0.dev0+git.211.g703f3654-windows-setup-unsigned.exe
Debian Package	kolibri_0.17.0a0.dev0+git.211.g703f3654-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.17.0a0.dev0+git.211.g703f3654.dmg
Android Package (APK)	kolibri-0.17.0a0.dev0+git.211.g703f3654-0.1.4-debug.apk
TAR file	kolibri-0.17.0a0.dev0+git.211.g703f3654.tar.gz
WHL file	kolibri-0.17.0a0.dev0+git.211.g703f3654-py2.py3-none-any.whl

[marcellamaki]

After reading through, the code changes make sense, but I get the following error when trying to navigate into an existing lesson. So, something with the state on the lesson summary page.

If I create a new lesson, I'm able to open the lesson page, and open up manage resources, etc.

I also tried on develop to confirm that this wasn't a regression that was introduce there, and I'm able to open the same (existing) lesson in my class without issue.

[marcellamaki]

Updates seem to have resolved the issue! Manual QA checks out -- thanks