Forward compatible changes to V3 custom schemas

[Rod Widdowson]

For the record:

Following conversations this week I have made the following changes to our
schemas

In the SAML Filter Schema (urn:mace:shibboleth:2.0:afp:mf:saml /
shibboleth-afp-mf-saml.xsd)

The following aliases are introduced (and we issue an INFO message if we see
the old style):

EntityAttributeExactMatch 	aliases
AttributeRequesterEntityAttributeExactMatch
EntityAttributeRegexMatchis	aliases 	AttributeRequester
EntityAttributeRegexMatch
NameIDFormatExactMatch	aliases
AttributeRequesterNameIDFormatExactMatch
InEntityGroup			aliases	AttributeRequesterInEntityGroup
RequestedAttributeInMetadata	aliases	AttributeInMetadata

RegistrationAuthority		replaces
AttributeRequesterRegistrationAuthority (which first appeared in the Alpha)

In the Security Schema (urn:mace:shibboleth:2.0:security /
shibboleth-security.xml):

The three, not previously implemented, ResourceBacked Credential or
ValidationInfo types are now implemented and take a SPRING resource (with
the defauklt being to file: as per the rest of our configuration).

X509ResourceBacked (Credential)
BasicResourceBacked (Credential)
PKIXResourceBacked (ValidationInfo)

The 3 Filesystem homologs are still implemented, but because they are edge
cases and are also 100% config. compatible with the ResourceBacked versions
they are deprecated and a WARN is issued.

The only question arising is how to document this.

I can enter JIRA cases for these changes, or I can amend the Alpha
Documentation with a "In all releases after the first Alpha" note.  Both are
not unprecedented, but I rather prefer the latter to the former (since my
95% prediction is that the Alpha documentation is going to morph into the
real documentation).

/Rod