Create setup.py to enable pip packaging/installation

[davelab6]

Would be good to have a setup.py script, so we could install this repo's tools via pip

[felipesanches]

Among the things I think would be in a pip package are:

• the python scripts that are currently spread on the root directory of this repo:

• The code in the util folder:

• At least these nam files (which are needed for New script: which characters in a TTF are not in any GF .nam subset? fonttools/fontbakery#1466):

• possibly more of the *.nam files that are spread on the encodings directory and its subdirectories.

[felipesanches]

The protobuffer generated file fonts_public_pb2.py in this repo is redundantly kept at the FontBakery repo as well.

[felipesanches]

I'd chmod a+x all the python scripts.

I would also consider if they can be included as modules on other python code when needed or if they are only useful as standalone scripts. I have to look more carefully at that yet, though.

[felipesanches]

In other words, packaging means we should come up with a good description of which tools the package provides, if they're meant for stand-alone usage on the command-line or as modules for other python programs, etc.

Right now this repo is a bit messy which seems to be a side-effect of how it grew organically in the past as demands for new helper scripts showed up. Not much different from the current state of the FontBakery helper scripts, actually.

[felipesanches]

I'll start by creating a setup.py for packaging the fontbakery helper/hotfix scripts that will be merged into this "tools" repo: fonttools/fontbakery#1639

After that, we'll add the scripts from this repo to that setup.py as well.

I suggest that we push this python package to PyPI under the name gftools (which stands for "Google Fonts Tools").