Move several KAS/KTS-IFC properties nested under scheme to the root of the registration

[Kritner]

Last time we checked there wasn't any actual cases of testing of the IFC flavors of KAS/KTS on demo, and due to that I had planned on changing the registration around a bit, namely:

Current KAS IFC registration:

root
    scheme1
        key generation methods
            modulo
            etc...
        etc...
    scheme2
        key generation methods
            modulo
            etc...
        etc...

where the above would allow a specifying of "key generation methods" on a "per scheme basis" where each "key generation method" could support multiple (and potentially differing) sets of modulo.

I'm not sure if it makes sense to have this complexity in the registration, and I've brought it up internally to perhaps change this part of the registration:

root
    scheme1
    scheme2
    key generation methods
    supported modulo
    etc...

so that the key generation methods are independent of the schemes, and the modulo are independent of the key generation methods.

I'm pretty sure this is a valid assumption to make, but up until now we hadn't had anyone testing this particular algorithm.

Originally posted by @Kritner in #942 (comment)