Make yarn version explicit and support alternate install method for docker compose

[bjester]

Summary

Description of the change(s) you made

• volta install yarn installed version 4.0.0-rc.37 which doesn't work properly because it attempts to install dev dependencies for KDS, creating a node/engine version conflict
• Adds check to Makefile to support either installation method for docker compose, since the new plugin method uses the command docker compose instead of docker-compose

Manual verification steps performed

1. Ran make dcbuild
2. Coordinated with @ozer550 on volta install yarn@1 and confirmed it worked

References

yarn issue

Packing kolibri-design-system@https://github.com/learningequality/kolibri-design-system.git#commit=e9a2ff34716bb6412fe99f835ded5b17345bab94 from sources
Using Yarn Classic for bootstrap. Reason: "__metadata" key not found in yarn.lock, must be a Yarn classic lockfile

➤ YN0000: Downloading https://classic.yarnpkg.com/latest.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-classic.cjs
➤ YN0000: Done in 2s 127ms

yarn install v1.22.19
[1/4] Resolving packages...
warning Resolution field "[email protected]" is incompatible with requested version "[email protected]"
warning Resolution field "[email protected]" is incompatible with requested version "[email protected]"
[2/4] Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version "10.x". Got "16.19.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. 

Comments

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• 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
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• 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

[rtibbles]

Interestingly, we only specify >= to in the Kolibri yarn restrictions, and yet this hasn't come up yet.

https://github.com/learningequality/kolibri/blob/develop/package.json#L62