Feature Request: Enhanced Error Handling for PID Provider Configuration

Overview of the Feature Request

After updating to Dataverse version 6.2, a configuration error occurred specifically when modifying domain.xml to support multiple PID providers. While the 404 handling has improved, I anticipated that errors due to missing or incorrect configurations would be managed by try/catch mechanisms to prevent application-wide impact. Enhancing error-handling layers around PID provider configurations would improve resilience, stability, and user experience.

What kind of user is the feature intended for?
Sysadmin, Developer

What inspired the request?
The need for resilience when implementing configuration changes for new PID providers.

What existing behavior do you want changed?
Rather than a generic error or application crash, more specific error messages and handling for misconfigurations in domain.xml and other files.

Any brand new behavior do you want to add to Dataverse?
Add targeted safeguards and error messages in cases of missing parameters or improper values specific to PID provider configurations.

Any open or closed issues related to this feature request?
Related to #10900 for improved 404 handling.

Are you thinking about creating a pull request for this feature?
I would be interested in test & contributing feedback to a solution if needed.

The issue names domain.xml and PID provider configuration, with related context in #10900. Start by reviewing those configuration paths and the existing 404-handling behavior. Before implementation, agree on which missing or invalid parameters must be caught and the expected messages; done means misconfiguration no longer crashes the application.