code linting as a PR quality check

[amnonkhen]

We should use linters to make sure our code is up to our quality standards.
Failure to meet the standard would disallow merge of the PR.

See discussion about linting rules

Acceptance Criteria:

• relevant errors
• not too many errors
• easy enough to inspect error messages

Tasks/Questions:

• should this be integrate with gitlab ci or as a github action? 1st step would be github action
• should disallow pr merge when there are errors
• rules for python - see .pylintrc and .flake8 files

for next steps:

• rules for java - do in ingest-core
• rules for javascript/typescript - for ingest-ui
• nice looking error report - 1st step is the text output of the linter

possible tools:

• super linter - will be used for 1st iteration, integrated as a github action
• code climate - seems we used it slightly in the past

[ESapenaVentura]

@amnonkhen to merge this today

[jacobwindsor]

@amnonkhen why is this still in waiting?