[CHORE]: add code and commit linting configs

[shavinac]

Code linting:

• Add an eslint file to app/ (see https://github.com/typescript-cheatsheets/react#linting)
• TBD / based on language decision - linting rules for iam/ and schemas/

Notable linting/formatting rules put in place:

• Double quotes, not single quotes
• Use semicolons
• Trailing commas always
• 2-space tab width
• 80-char recommended line length
• no unused variables
• (warning-level) should explicitly annotate function return types, even if the return type can be inferred.

--

Commit message formatting:

• https://www.conventionalcommits.org/en/v1.0.0-beta.2/
• https://commitizen-tools.github.io/commitizen/ (CLI tool to generate Conventional Commits)
• https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/cz-commitlint - adapter for commitizen to use commitlint config

Question:

• should we enforce including lerna package as scopes? https://github.com/conventional-changelog/commitlint/tree/master/@commitlint/config-lerna-scopes

[farque65]

Closed by: #20