OpenSAML now requires valid min/max refresh rates

Running the Selenium tests resulted in all tests failing after the execution of any test that manipulated a File-Backed HTTP Metadata Resolver/Provider. The error would look like the following:

Caused by: org.springframework.beans.factory.BeanCreationException: 

Error creating bean with name 'metadataResolver' defined in class path resource [edu/internet2/tier/shibboleth/admin/ui/configuration/MetadataResolverConfiguration.class]:

Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException:

Failed to instantiate [org.opensaml.saml.metadata.resolver.MetadataResolver]:

Factory method 'metadataResolver' threw exception; nested exception is net.shibboleth.utilities.java.support.component.ComponentInitializationException:

Minimum refresh delay PT5M is greater than maximum refresh delay PT1M

This is odd because these values were not the values set in the FBHTTPMP. Furthermore, the test creating the FBHTTPMP itself passes. It's only subsequent tests that fail. It was determined as well that any test that manipulates a FBHTTPMP will cause any test after it to fail. If the FBHTTPMP tests are disabled, then the rest of the test suite passes without issue.

Investigate the changes in OpenSAML as they pertain to Min/Max Refresh Delay and the FBHTTPMP (and any other affected MPs) and update the code as necessary for it to be conformant.