Parsing relying-party

[Rod Widdowson]

A short follow up from Friday's mail about security configuration for the
profiles.

Assuming that I have fixed the regressions in Jenkins I believe that the
parsing of the relying-party.xml is now close to being at a stage where we
have all that we absolutely need to ship an Alpha release.  

For the record I think that the following is still needed (in my perceived
order of importance).

- Wire the real RP resolver into the configuration.  That’s what is up next.
- The open issues in other mail threads about wiring in Predicates for
signing and encryption.
- The Liberty SSOS profile (are there any others I have missed?)
- Allowing the parsing a file which only contains a <MetadataProvider>, thus
completing the work to separate metadata configuration from RP
configuration.  The legacy case of having both inside relying-party is what
currently works and will continue so to do.
- As per the thread last week, more Trust engine parsers are required (even
the ones we will not support will need to generate a warning).
- Code cleanup to centralize <Credential> parsing and to rely more heavily
on Cryptacular (as per discussions in previous team meetings).
- Code coverage in the parsers.

We could probably ship a first Alpha with only the first completed.

/Rod