Odoo-tools

Revert the setuptools to <58. Setuptools will silently ignore use_2to3 for [58.0.0](https://setuptools.pypa.io/en/latest/history.html#v58-0-0)

> [2086](https://github.com/pypa/setuptools/issues/2086): Removed support for 2to3 during builds. Projects should port to a unified codebase or pin to an older version of Setuptools using [PEP 518](https://peps.python.org/pep-0518/) build-requires.

But will only fail a build at [v58.0.2](https://setuptools.pypa.io/en/latest/history.html#v58-0-2)

> [2769](https://github.com/pypa/setuptools/issues/2769): Build now fails fast when use_2to3 is supplied.

Nothing else changed except the requirements and cleaned up pip install vatnumber that is already in the requirements for odoo13. Technically we could also have a fork of vatnumber that doesn't really validate anything and can be used transparently. If you really want to ensure that the tax number are valid, you should really use proper APIs instead of the vatnumber validation.

The current github workflows have been updated to work with odoo13 after some changes at github. It seems that for some reasons, it's not possible to install vatnumber with pip>=23 on the current ubuntu images.

It's unclear what is preventing this but for that reason the version of pip is downgraded to <23 for odoo13. It's possible that I'll drop support for odoo13 and less as it require to manipulate the version of setuptools to be less than 58 due to the modules using use_2to3.

Fixes:

- It's possible to exclude modules from the output of `module deps` to only see the dependent modules but not the one that are already included in the lookup. For example, if you wanted to test a,b,c,d and you had c depending on a,b; and d depending on c. You would want to have only a and b as dependencies of c,d. This can then be sent to odoo to install a and b without tests and then install c and d with tests.

- platform.processor seems to have changed behaviour and now may return an empty string. It now use platform.machine as a fallback.

- addons_path would parse invalid paths containing whitespace at the start or end of the path. Now the paths are stripped to make it possible to.

In this version of odoo-tools, a new API has been integrated to host odoo servers. It's still more or less a draft of what would become a more sophisticated way to run odoo. The new API is modular and can be extended to support different kind of setup.

It is designed as a set of mixins that can be used to build a custom wsgi application or potentially different kind of entrypoints to run cron or execute commands from command line.

Ideally, this will replace parts of Odoo-tools that execute Odoo directly as this OdooApplication is able to configure things outside of the what's possible with odoo.tools.config. One other important aspect is that using the API means that some part of odoo will get overriden by a custom patches available as module overlays in odoo_tools.overlays.

This is the kind of change that's likely to happen for a version 0.2 or potentially 1.0.