Feature Request/Idea: Classify metadata fields as mandatory, recommended, and optional #6885

Overview of the Feature Request
As an installation admin, I'd like to be able to classify metadata fields as mandatory, recommended, and optional in any sub-dataverse (as opposed to the current two choices of mandatory and optional fields). Mandatory and recommended fields should pop up at the initial step of creating a dataset. The possibility to classify metadata fields as recommended and make them appear in the first round of metadata registration would make it much easier to get depositors filling in these fields.

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

What inspired the request?
Currently, our curators often have to make depositors aware of there being other important metadata fields than the mandatory ones.

What existing behavior do you want changed?
The fact that currently only mandatory (and a few other) metadata fields are displayed in the first round of metadata registration.

Any brand-new behavior do you want to add to Dataverse?
Yes, the feature request introduces a new option of classifying/prioritizing metadata fields.

Any open or closed issues related to this feature request?

• https://github.com/IQSS/dataverse/issues/6885

Start by reviewing the current metadata registration flow in the dataverse-frontend repository and the related Dataverse issue #6885. Identify how fields are currently classified and which fields appear in the initial dataset-creation step. Done means supporting mandatory, recommended, and optional classifications in sub-dataverses, with mandatory and recommended fields shown initially.