Update Developer Setup Guide to include instructions on pulling submodules.

[plarocque4]

Describe your changes

Update Developer Setup Guide to include instructions on pulling submodules.

Issue ticket number and Jira link

REMS-369

Checklist before requesting a review

• I have performed a self-review of my code
• Ensure the target / base branch for any feature PR is set to dev not main (the only exception to this is releases from dev and hotfix branches)

Checklist for conducting a review

• Review the code changes and make sure they all make sense and are necessary.
• Pull the PR branch locally and test by running through workflow and making sure everything works as it is supposed to.

Workflow

Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.

[KeeyanGhoreshi]

we can ignore the failing tests for now since the switch to mocha should take care of the strange errors jest is giving.

When I pulled the submodule I had to run git submodule update --remote after the init to actually get the submodule on the branch I wanted it to be on. I think it might also be helpful to add a note about troubleshooting, since I had to use https to get it to run with git submodule sync.