Feature Request/Idea: Make dataverses metadata configurable

Overview of the Feature Request

Make dataverse collections metadata configurable.

What kind of user is the feature intended for?
Instance administrators for the configuration and dataverse collections creators/administrators for the end-use.

What inspired the request?
Dataverse for research units or project with multiple affiliations and the will to specify other dataverse types.

What existing behavior do you want changed? / Any brand new behavior do you want to add to Dataverse?
Allow to change the metadata of a Dataverse via an external configuration file in a similar manner to the tsvs for the datasets metadata.

With the main objectives being :

1. making affiliation multiple (maybe this could be done with the current system without the effort of externalizing the dataverses metadata)
2. editing the dataverseType list
   https://github.com/IQSS/dataverse/blob/6ca1c9d873218cb1e28f8443e7e242912ae09c8f/src/main/java/edu/harvard/iq/dataverse/Dataverse.java#L75-L77

Any open or closed issues related to this feature request?

None that I found, surprisingly.

Start with the Dataverse.java dataverseType and affiliation definitions linked in the issue, then inspect how dataset metadata TSV configuration is handled. Determine the configuration format and behavior needed for multiple affiliations and an editable dataverseType list. Done means instance administrators can supply external metadata configuration that creators and administrators can use.