10476 display on create field option

[Saixel]

What this PR does / why we need it:

This PR introduces the displayOnCreate property to the DataverseFieldTypeInputLevel class, allowing administrators to configure metadata fields to appear during dataset creation, even if they are not required.

Previously, metadata fields selected for a collection would only appear during dataset creation if they were marked as required (or displayOnCreate by default). This change grants collection administrators control over metadata visibility, improving metadata completeness and discoverability.

Which issue(s) this PR closes:

• Closes Ensure Visibility of Non-Required Metadata Blocks on Dataset Creation #10476

Special notes for your reviewer:

This PR implements the functionality for displayOnCreate, but the UI implementation is not included yet.

If you want to temporarily enable a checkbox for testing, you can manually add the following code snippet at line 384 of dataverse.xhtml. This will render a checkbox in the collection settings UI to toggle the displayOnCreate property:

<td>
    <p:selectBooleanCheckbox id="DisplayOnCreate#{dsft.id}" 
                             value="#{dsft.displayOnCreate}" 
                             widgetVar="DisplayOnCreateOpt#{dsft.id}" 
                             disabled="#{DataversePage.editInputLevel == false}"
                             rendered="#{!dsft.hasParent and (!dsft.required or (dsft.hasParent and !dsft.parentDatasetFieldType.required))}">
        <p:ajax update="@widgetVar(DisplayOnCreateOpt#{dsft.id})" 
                listener="#{DataversePage.updateDisplayOnCreate(mdb.id, dsft.id, dsft.displayOnCreate)}" />
    </p:selectBooleanCheckbox>
</td>

Once the UI implementation is complete, this manual addition will no longer be necessary.

Suggestions on how to test this:

1. Create or edit a collection.
2. Navigate to the metadata fields selection section.
3. Verify that the displayOnCreate checkbox appears next to metadata fields.
4. Enable displayOnCreate for a field and save the configuration.
5. Create a new dataset in the collection and confirm that the selected metadata field appears in the dataset creation form.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No UI changes in this PR. A separate issue will track the UI implementation.

Additional documentation:

[coveralls]

coverage: 22.737% (-0.03%) from 22.762%
when pulling c27a51d on 10476-display-on-create-field-option
into 3aea148 on develop.

[stevenwinship]

My concern with this is that the displayOnCreate isn't passed in to the constructor.
This means that the value isn't able to be passed from Dataverses.parseInputLevels.
export JSON='[{"datasetFieldTypeName":"geographicCoverage", "required":true, "include":true}, {"datasetFieldTypeName":"country", "required":true, "include":true}]'
API /api/dataverses/$ID/inputLevels

[stevenwinship]

I would also like to see a test where the displayOnCreate is set and retrieved vis API

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:10476-display-on-create-field-option

ghcr.io/gdcc/configbaker:10476-display-on-create-field-option

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[stevenwinship]

Please address the merge conflicts along with the review comments. Thanks