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.

The implementation includes:

• New property displayOnCreate in DataverseFieldTypeInputLevel
• API endpoint to update the displayOnCreate setting
• Integration tests to verify the functionality

Testing via API:

1. Create a test collection:

curl -X POST -H "X-Dataverse-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{
  "name": "Test Collection",
  "alias": "test-collection",
  "dataverseContacts": [{"contactEmail": "[email protected]"}],
  "metadataBlockIds": ["citation", "socialscience"]
}' \
http://localhost:8080/api/dataverses/:root

2. Configure a field to display on create:

curl -X PUT -H "X-Dataverse-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '[
  {
    "datasetFieldTypeName": "unitOfAnalysis",
    "required": false,
    "include": true,
    "displayOnCreate": true
  }
]' \
http://localhost:8080/api/dataverses/test-collection/inputLevels

3. Create a dataset in the collection and verify that the field appears in the creation form.

Automated Tests:

Run the integration test:

mvn test -Dtest=DataversesIT#testUpdateInputLevelDisplayOnCreate

Does this PR introduce a user interface change?:

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

Additional documentation:

[coveralls]

coverage: 22.724% (-0.01%) from 22.736%
when pulling 4625a3a on 10476-display-on-create-field-option
into 2210d16 on develop.

[stevenwinship]

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

[ofahimIQSS]

This PR has a merge conflict.

[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.

[Saixel]

@stevenwinship @ofahimIQSS I have added all the adjustments and the test.
I have also finished resolving the conflicts.
Let me know if any adjustments are needed!