Use tox to test on all envs

As suggested in https://github.com/nexB/commoncode/pull/30#issuecomment-910526284 by @vznncv

> I'm closing this pull requests since @pombredanne has proposed better solution.
>
> @pombredanne Did you consider [tox](https://tox.readthedocs.io/en/latest/) usage instead of `configure` scripts? Generally it does the same things (virtual environment creation for tests), but has additionally features like [generative envlis](https://tox.readthedocs.io/en/latest/config.html#generative-envlist) that allows to test a library with different dependency versions.

@pombredanne replied:
>> Tox in addition would help! +1
>> Note that ./configure does a setup that's also useful beyond testing

So recap:
1. we should use tox
2. this may need to update on the CI setups to use tox too
3. we would still keep configure IMHO
4. we could consider tox to also test multiple versions of key dependent packages to handle issues such as https://github.com/nexB/commoncode/pull/30
5. we could consider tox to also test with the latest versions of all dependent packages