story(evrys): define contributing guidelines

[Zaba505]

Description

As a contributor, I want to know the expectations for making a contribution, so that I can easily make a contribution.

Acceptance Criteria

• Document code styling
• Document agile practices
• Define commit message standards
• Define other expected "best practices"
• Also define developer standards in separate file

Related Issues

No response

[Zaba505]

@erictg Definitely feel free to add to this list so we can track code standards for now

Define a section for development standards:

• Never create a util, common, or other generic name package
• Always "minimally" wrap any error before returning it
• Don't include method/function calls in assert statements for better readability