Refactor test and lint to use templated command

[novopl]

What?

docs:
  path: docs
  command:
    sphinx-refdoc  \
      -i src/peltak \
      -i src/peltak_appengine \
      -i src/peltak_django \
      -i src/cliform \
      \
      {opts.verbosity | count_flag('-v')} \
      docs/ref; \
    sphinx-build \
      -b html \
      -d {cfg.build_dir}/docs \
      docs
      docs/html


checks:
  - name: Check static types
    command: mypy {files}
  - name: PEP8 compliance
    command: pycodestyle --config ops/tools/pep8.ini {files}
  - name: Static code checks
    command: pylint --rc-file ops/tools/pylint.ini {files}


tests:
  unit: |
    pytest -c ops/tools/pytest.ini \
      --cov-config=ops/tools/coverage.ini \
      --cov={cfg.src_dir} \
      --cov-report=term \
      --cov-report=html:.build/coverage \
      --junitxml={cfg.build_dir}/test-results.xml
      --full-trace
      -vvv
      test/unit

Why?

Pros:

• It could greatly simplify the peltak code base
• Could be way more flexible
• Makes you remember the actual tool commands

Cons:

• You have to write the command yourself, peltak won't help you with that (less beginner friendly).

How?

It could be implemented using jinja2 for the command templates. The template rendering doesn't have to be super fast because it only happens when the actual command is ran and that will take much more time to execute.

The command template should be injected with a standardized environment that contains everything needed (options, conf, filters, etc.).

The base code for that can be developed when working on the scripts.