Feature Request/Idea: Consider error handling when trying to load metadata block where field's allowControlledVocabulary property is TRUE but vocabulary terms are missing

Also maybe the Dataverse software can return some error when it tries to load a TSV file that has any fields where allowControlledVocabulary is TRUE but no terms are listed for that field in the TSV file's #controlledVocabulary section.

Overview of the Feature Request
When an installation manager tries to load a metadata block TSV file that has a field whose allowControlledVocabulary property is TRUE, but there are no vocabulary terms for that field in the TSV file's #controlledVocabulary section, the Dataverse software doesn't load the metadata block and returns an error to let the installation manager know.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Sysadmin

What inspired the request?
https://github.com/IQSS/dataverse/issues/8857

What existing behavior do you want changed?
The Dataverse software lets an installation manager load a metadata block TSV file that has a field whose allowControlledVocabulary property is TRUE while there are no vocabulary terms for that field in the TSV file's #controlledVocabulary section.

Any brand new behavior do you want to add to Dataverse?
When an installation manager tries to load a metadata block TSV file that has a field whose allowControlledVocabulary property is TRUE, but there are no vocabulary terms for that field in the TSV file's #controlledVocabulary section, the Dataverse software returns an error to let the installation manager know.

Any open or closed issues related to this feature request?

• https://github.com/IQSS/dataverse/issues/8857
• https://github.com/IQSS/dataverse/pull/9984

Start by tracing Dataverse's metadata block TSV loading and #controlledVocabulary parsing, using issues 8857 and pull request 9984 for context. Done means a metadata block with allowControlledVocabulary set to TRUE but no terms for that field is rejected with an informative error, while valid blocks continue to load.