(doc) update design documentation and decisions

[klinkoberstar]

This PR updates the design documentation and will close #139

Describe your changes

This is a documentation PR and does the following:

• Creates design.md in the decisions folder to document key decisions
• Creates a design folder in docs that contains:
  • a folder with wireframs
  • a readme which outlines the design principles for the project and links out to other resources to help better understand the design process (i.e. wireframes, decisions etc)
  • Creates a file with a summary of meeting notes with our partners to document the source of many of our design decisions
• adds project values from M2 into the docs folder.

Checklist before requesting a review

• [X] pre-commit run --all-files (run before pushing)
• [X] pytest if applicable
• [X] Link issue
• [X] Update relevant documentation if applicable: doc strings, readme, poetry.

[xiomara0]

This looks great to me. Added two changes:

• fixed Jesús' name
• added another example to "Build Slowly and Scalably"

I was wondering if we need to elaborate on an example for this principle - User centered: New Migrants and Community Based Organizations are the designers, our role is to execute what they need. Like when we have design decisions, we ultimately ask the domain knowledge org for their opinion and roll with it. Not necessary tho, but unsure if we should write that out so it's explicit.