Expose vue composition api through apiSpec (kolibri.lib.vueCompositionApi), so it is available to all SPAs

[jonboiser]

Summary

The original PR that brought Vue Composition did not properly install the plugin for all SPAs (for reasons I don't understand). However, if it is bundled into apiSpec and exposed via kolibri.lib.vueCompositionApi, it works 🤷

So this PR

1. Makes kolibri.lib.vueCompositionApi the primary way to import Vue Composition API into your components
2. Refactors Device, Coach, User, and Facility plugins to use the composition in a small way (to give us early warning if something goes wrong with the plugin)

References

This issue is blocking #8137 , since the current implementation makes heavy use of the composition API.

Reviewer guidance

Again, this refactor is a pretty straightforward mapping of Vue options -> composition functions, with a little sugar from vueuse/core. The app should work exactly as before.

---

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