Feature Request: Add Dataverse support for customizing placeholder text used by the external controlled vocabulary functionality

Overview of the Feature Request
Dataverse itself needs to able to support the customization of the placeholder text (or watermarks) used by the external controlled vocabulary functionality, so that installations can more easily change the placeholder text, without having to fork the script used by the external controlled vocabulary functionality, and so that text can more easily be translated and displayed in other languages.

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

What inspired the request?
The placeholder text was adjusted when the external controlled vocabulary functionality was used to change metadata fields on Demo Dataverse (see https://github.com/IQSS/dataverse.harvard.edu/issues/327).

In that GitHub issue, @qqmyers wrote that the "ability to customize the placeholder dynamically is supported by the scripts, but evidently not in Dataverse itself," and that Dataverse will need to support customization of the placeholder text too so that Dataverse installation admins don't need to fork the script used by the external controlled vocabulary functionality, and so that the text can more easily be translated and displayed in other languages.

Any open or closed issues related to this feature request?

• https://github.com/IQSS/dataverse.harvard.edu/issues/327
• https://github.com/IQSS/dataverse.harvard.edu/issues/326

Start by reviewing the external controlled vocabulary functionality and the related issues 327 and 326 to understand how placeholder text is currently supplied. Define the configuration and translation requirements for Dataverse installations, with completion meaning admins can customize the placeholder without forking the script and users can see localized text.