Overhaul Tern's continuous integration testing

[rnjudge]

Describe the Feature
Currently Tern uses ci/test_files_touched.py to run various Tern tests based on which files were changed in a commit. This way of testing has proved to be porous, however, and many regressions have not been caught. Examples of errors that have been introduced with new commits but not caught with the test_files_touched scripts:

• Output report stops collecting packages for certain package managers (Tern not collecting go modules #924 )
• Output report changes -- i.e. adding duplicate notices to the report (Fix duplicate OS notices #927)
• Loading from the cache causes unexpected output report content (Debian dockerfile reports duplicate packages #899)

Use Cases
This will be helpful to catch bugs before they are introduced to the code base instead of after the fact.

Implementation Changes
We should test all of the code no matter what files were changed. We should also be verifying the contents of the reports, not just making sure that the reports are generated.

Related Issues*

• Use commitlint to lint commits #914

[nishakm]

@rnjudge would this be a good issue to complete for the Beta release?