Create GitHub actions workflow to run ci process 499

[fabulouiOS-monk]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

Added .yaml file for running unit test in github workflow.

Related issue

• Create GitHub Actions workflow to run CI process #499

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and iOS rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-iOS repo

• The linting and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[fabulouiOS-monk]

@andrewtavis, The test pipeline is now working fine. But It's taking 8 mins to build and run. Need to see what we can do.

[andrewtavis]

How are you feeling about it at this point, @fabulouiOS-monk? :)

[andrewtavis]

#500! Fitting that it's you sending it along, @fabulouiOS-monk, and also that it's such a major step for Scribe-iOS 😊 Really appreciate your dedication to the project!

Thanks also @vickcoo for the tests here! Really off to a great start!

[andrewtavis]

Note also that org naming conventions are we name the workflows after the file, but we can talk about this if we would like to give them a title rather than the file :)

[andrewtavis]

Added a name: to the workflow just now so it's a bit more descriptive :)