fields in track.json

[IzzySoft]

While most of the fields requested in #7 and became available with v2.0.0 (thanks a lot!), 3 fields have been left out: antifeatures (array), category (str) or categories (array/CSV) and translation. The former two are essential for my repo:

• antifeatures: as my repo is focused on FOSS and privacy, "borderline-cases" (e.g. a module having proprietary components or depending on such) need to be clearly marked.
• category/categories: especially with larger repos (mine currently holds 82 modules) this helps narrowing down the list to the area you need a module for. With my repo e.g. filtering on "Multimedia" narrows down results to 7, or "Theming" to 6 out of the 82 modules.

Both of these are already used with my repo, which you can see here in its web interface. It's a "custom hack" I'd prefer to have supported "officially". So if you could just integrate these 2 fields that would be great; translation (linking to where one can support localization of a module e.g. via Crowdin, Transifex, Weblate etc) seems o be rarely offered by module developers (only 2 out of the 82 modules in my repo have this) – so while it would be nice-to-have, it's not as essential as the other two and I'd simply drop it if you'd at least integrate the former 2. For categories I'd suggest the "plural" variant, either using a string of comma-separated values or an array, whatever suits you best; antifeatures should be an array as sometimes multiple of them must be applied.

Thanks again for all your great work – and for considering this addition!