Model JCA providers individually

[kruegers]

As of now, there are rules for the JCA. However, "the JCA" in its default configuration actually comes as a set of individual providers.
Create one project for each of the providers and model their usages. Once that is done, remove the JavaCryptographicArchitecture project from the repo.

[johspaeth]

I even suggest to introduce some versioning in form of the folder structure (With version I mean the version of the library that has been specified and not the version of the ruleset itself.)

We currently have specified BouncyCastle in version 1.6.

We could have a subfolder for each version, similar to how maven handles versions:

BouncyCastle\1.6\

Do we need similar logic for the JCA?