Investigate feasibility of super linter GH workflow

[pallasite99]

The idea here is to basically have one workflow internally call the static checks required for a commit to a repo.

Ex: If I make a change only to a json file, I don't need to run a go static check.

This is done by a GH action called super linter, which does all of this internally after getting triggered during the action config specified. More info here:

https://github.com/github/super-linter

An example of this (check commit history):

https://github.com/pallasite99/customer_risk_analysis_api

This will make our CI workflow simpler and only run what is required, instead of POs commenting out or deleting unneeded workflows manually.