issue/209 - Migrate from npm to yarn for package management

[Matteas-Eden]

Both the front-end and back-end have been migrated from npm to yarn, which involved removing their respective package-lock.json and running yarn install to generate the yarn.lock file. Future installations should use yarn install --frozen-lockfile. The relevant documentation has been updated to reflect the change in package manager, and all front-end tests have passed. Due to #211, the back-end tests could not be run. They should run fine, but this will need to be evaluated by a reviewer as part of the approval process.

Closes #209 Closes #215

• [ ] The pull request is complete according to the following criteria:
  • [x] Acceptance criteria have been met
  • [x] The documentation is kept up-to-date
  • [x] Comprehensive tests (if applicable) have been generated and all pass.
  • [x] The pull request describes the changes that have been made, and enough information is present in the description for any developer to understand what has changed
  • [x] Commits have been squashed (or will be on merge).
  • [ ] The branch name is descriptive and follows the pull request title format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
  • [x] The pull request title is of the following format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
  • [x] The description uses github syntax to link to the issue. E,g Resolves se701g2/Doto#{Number}
  • [ ] At least two reviewers assigned. One of which must be the assigner of the issue.
  • [ ] If there are merge conflicts, run git rebase as opposed to git merge with master.

[jordansimsmith]

Nice change @Matteas-Eden, you will have to modify the workflow too.

[Matteas-Eden]

@all-contributors please add @Matteas-Eden for code, review, design, doc, test

[allcontributors[bot]]

@Matteas-Eden

I've put up a pull request to add @Matteas-Eden! :tada: