Please notice a CLI change - opsmop policy files now *are* their own command lines


#1

Because of some implementation details involving pickling, I needed to stop using "run_path", which means that now instead of the .py file being a parameter to bin/opsmop, the opsmop policy files are once again executable, like this:

policy.py --local --apply
policy.py --local --check

See here:

https://docs.opsmop.io/local.html

I can probably make it so that the system will automatically chdir into the directory of the script, but right now all paths are still relative to cwd. This will probably change in the near future so it doesn't matter what directory you are in.