Remove relative imports, use "best practices" python module importing

[schuylermartin45]

As discussed in the last meeting, and exemplified by this PR we need to move away from using relative Python imports and use the "best/fully-sanctioned" method of managing Python modules in a project.

I've run into Python module issues several times in my career and I can never remember exactly what "the right way" to do it is, but I think we have to setup the directory structure such that there is one top-level module so that all submodules can "see" each other.

Something along the lines of:

src/
|-- anaconda-linter/
  |-- run.py
  |-- lint/
    |-- check_foobar.py
  |--...
|-- scripts/
  |-- foo.py
  |-- bar.py
  |-- ...
test/
|-- test_blah.py
|-- ...

The most important part is I think we have to remove all uses of relative imports. I believe that is the root cause of most of our current module issues.

[schuylermartin45]

I did this a few weeks ago. Closing.