Add harvesting feature to handle missing controlled values

[stevenwinship]

What this PR does / why we need it: Allows datasets to be harvested with Controlled Vocabulary Values that existed in the originating Dataverse Project but are not in the harvesting Dataverse Project.

Which issue(s) this PR closes: #9992

Closes #9992
Special notes for your reviewer:
Suggestions on how to test this: See HarvestingClientsIT.java for examples.

Does this PR introduce a user interface change? No

Is there a release notes update needed for this change?: in 9992-harvest-metadata-values-not-in-cvv-list.md

Additional documentation:

[coveralls]

coverage: 20.57% (+0.3%) from 20.262%
when pulling 5bb189b on 9992-harvest-metadata-missing-controlled-values
into f456e51 on develop.

[landreev]

I'm leaning towards just approving this, not seeing anything to nitpick on.
@qqmyers thanks for the detailed input on the parsing/indexing earlier. Reading the current code there, it appears to be doing what we want, but please take a quick look/give it a thumbs up, just in case.

[landreev]

Looks great.

[sekmiller]

Do we care that there's not a UI change for this? That is when I set up a new client via the UI we aren't allowed to set the new param, nor do we see its value in the in the list of completed clients. Works fine when setting up client via api or if you modify the param directly in the db.

[sekmiller]

Maybe we should say something about the new setting here: https://guides.dataverse.org/en/6.1/admin/harvestclients.html

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:9992-harvest-metadata-missing-controlled-values

ghcr.io/gdcc/configbaker:9992-harvest-metadata-missing-controlled-values

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