Release v0.18 breaks codepoints
With release v0.18 the codepoints of the logos in the `ttf` font have changed. That means, that a person who uses a symbol with v0.17 needs to adapt after updating.

![image](https://user-images.githubusercontent.com/16012374/151007716-b90a1bc8-1d12-4321-8831-6252d145ca0c.png)

This commit https://github.com/lukas-w/font-logos/commit/f161cf60da18815780bc48dacc0810490a1a8dfd removes the file `.fontcustom-manifest.json` (and prevents re-adding by putting it into `.gitignore`, so it is not by accident?!). But that file defines which glyph gets which codepoint.
If the file is not existing the glyphs are added in alphabetical filename order.
That will shuffle the logos' codepoints whenever new logos are added.

This has happened in the past already sometimes, but the question is if this is what users of the font file would want.
If you have any document or commandline prompt or other use of the font file and update the font file the contents changes.

**Suggestion: Keep codepoints of a certain logo constant and just add new logos in the end (or in vacant spots).**

In  the whole history of `font-logos` there has been only 3 of this breaking codepoint re-enumerations:

* v0.1 -> v0.2 (February 2016, v0.1 was a tagged pre-release, so this might be ok)
* v0.9 -> v0.10 (Jan 2018, renaming from `linux` to `logos`, so this might be ok)
* v0.17 -> v0.18 (July 2021, ... reason unknown)