SHIBUI won't startup with existing External Metadata Resolver

Scenario:

1. Create a testbed environment from the develop branch using Java 11.
2. Login as the admin and create content for all the different features.
3. Kill your SHIBUI docker container but keep the db and mailhog containers running.
4. Create a new testbed environment on the feature/shibui-2508 branch using Java 17.

Issue: The SHIBUI container won't start up. I am seeing the following error in the logs for the MySQL DB:

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'JPAFilterServiceImpl': Unsatisfied dependency expressed through field 'metadataResolverService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'JPAMetadataResolverServiceImpl': Unsatisfied dependency expressed through field 'metadataResolver'; nested exception is 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 java.lang.RuntimeException: Unsupported metadata resolver type!

I verified this issue is also occurring with the Postgres DB.

I verified this is not a Java 11 to 17 issue, but an issue with starting shibui with a specific set of data existing.

Scenario:

1. Create a system with a persistant DB and create an External Metadata Resolver.
2. Stop Shibui
3. Restart Shibui - should fail