docs: Add Prettier note on Contributing doc

[menina763]

Description

Include a text about having Prettier installed and reminder to run write and check functions on current file(s).

Fixes #317

Type of Change:

• Documentation

How Has This Been Tested?

Checklist:

• My PR follows the style guidelines of this project
• I have performed a self-review of my own code or materials
• I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Any dependent changes have been merged

[menina763]

@brittanyjoiner15 Soo I may just contradict the very things that I wrote in the doc lol. Umm should I get rid of this PR and try to have Prettier installed? I'm afraid that I may have messed up on it.

[isabelcosta]

@Menina294 this is looking good :) I think you could also include a section on the README, explaining is the command to install and run prettier. You could do:

### Run linter

To install linter run this command: `yarn install prettier`
To run, use this command: `prettier ...`

I am not sure what are the exact commands, but this is an idea of how it could look like :)
cc @brittanyjoiner15

[brittanyjoiner15]

@isabelcosta and @Menina294 we actually might want to put this on hold until we figure out what's happening with #325 - just in case that changes anything, but yes in general I think you probably should just need some lines like @isabelcosta drafted above! I think the additional line would be the prettier write command, which I'm adding in here:

### Run linter

To install linter run this command: `npm install --save-dev --save-exact prettier` or `yarn add --dev --exact prettier`
To lint the code, run `npx prettier --write .` or `yarn prettier --write .` or `

@Menina294 let me know if you need any help with the commits and stuff! I know it's a little nerve-wracking sometimes. I prefer using the Github Desktop client, because it helps make it more clear! But basically you'll create a new branch, then make changes to your code in your editor (basically adding the section above into the contribution.md file), and then in the Github desktop you can just push that blue button in the bottom left that says "commit changes", and then it will pop up another blue button in the middle/top of the app that says "publish branch" and then "create pull request". Click each of those and it will open up a page in here to create a PR. Just fill out that info, and you'll be good to go!

[menina763]

Ahh okay. Thanks for letting me know @brittanyjoiner15!