RP config status

[Cantor, Scott]

I got back to this last night and this morning, and I guess maybe this was
a formality, but it's pretty clear the native format is going to be much
simpler to use than the current schema, so I don't think this is really
much of an open question.

All of the actual implementation class names are now inside a system file
that has parent beans for all of the relevant pieces of configuration, so
we're not exposing those classes directly. I'd like to work on that more
across other files so that as few classnames as possible are embedded in
user configuration. That's my biggest concern with the Spring files in
general.

It may be worth creating some shorthand constructors that auto-generate
common predicates to use as conditions for the relying party definitions.
The conditions are about the only inelegant syntax, so if we could smooth
that over for some common cases, that would help.

-- Scott