Split RetDec support package

The current RetDec support packages contain the following:
- Ordinal numbers for Windows libs.
- Crypto signatures in text YARA format.
- Library type information in JSON format.
- Statically linked code signatures in compiled YARA format.

We should split these for better design and treat them differently.

These two would be better of under a version control in RetDec git:
- Ordinal numbers for Windows libs.
- Crypto signatures in text YARA format.

Compile text YARA crypto signatures at the installation step.

These two are auto generated from massive number of files and there is no reason to keep the generated results under version control. However, we should split them into two support packages, since their update cycle is not the same:
- Library type information in JSON format.
- Statically linked code signatures in compiled YARA format.

The issue names no files, tests, or entry points. Start by locating the four RetDec support-package definitions and the installation/build configuration that handles YARA data; done means the two versioned resources are separated, text YARA is compiled at installation, and the two generated resources have independent packages.

Written by the indexing model from the issue text.