8094 java17

[poikilotherm]

What this PR does / why we need it:

Enable usage of Java 17. Lots of good new stuff, better GC etc.

Which issue(s) this PR closes:

Closes #8094

Special notes for your reviewer:
Remember to use Java 17. Maybe https://sdkman.io is of interest for you?

Suggestions on how to test this:
TODO

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

Is there a release notes update needed for this change?:
Yes. Not yet included.

Additional documentation:
TODO

[poikilotherm]

A few (6) API tests are broken:

[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   DatasetsIT.testExcludeEmail:738 expected:<[]> but was:<null>
[ERROR]   DatasetsIT.testExport:590 1 expectation failed.
JSON path data.latestVersion.metadataBlocks.citation.fields[2].value[0].datasetContactEmail.value doesn't match.
Expected: sammi@sample.com
  Actual: null

[ERROR]   DatasetsIT.testReCreateDataset:2509 1 expectation failed.
Expected status code <201> but was <403>.

[ERROR]   DatasetsIT.testSemanticMetadataAPIs:2407 https://dataverse.org/schema/citation/datasetContact
Expected: https://dataverse.org/schema/citation/datasetContactEmail
     but none found

[ERROR]   HarvestingServerIT.testMultiRecordOaiSet:606 Wrong number of items on the first ListIdentifiers page expected:<2> but was:<5>
[ERROR] Errors: 
[ERROR]   DatasetsIT.testPrivateUrl:964 » Connect Verbindungsaufbau abgelehnt (Connectio...
[INFO] 
[ERROR] Tests run: 193, Failures: 5, Errors: 1, Skipped: 8
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  11:10 min
[INFO] Finished at: 2023-01-16T23:22:45+01:00
[INFO] ------------------------------------------------------------------------

[mreekie]

Grooming:

This issue was in the New or No Status columns on the Dataverse Global Backlog Board.
Those columns have been removed.
This issue has been removed from the board

This is NOT a reflection of the priority of these issues.
However, as we have worked on the grooming process, it became clear that these issues which are in columns that are not stewarded will likely not get prioritized or sized.

To get this item onto the Dataverse Global Backlog Board, please reach out to one of the Stewards on the board.
You can also reach out to @mreekie and I can connect you with the steward of the appropriate queue

[pdurbin]

We aren't sizing this yet. @poikilotherm is going to hack some more. Thanks! 🎉

[mreekie]

Grooming

• Including as part of Payara 6 upgrade deliverable

[mreekie]

Sizing:

• This cannot be completed until 5.14 is released.
• The next small step that can be done here is resolving file conflicts.
• This will be put off until we work through the Payara6 upgrades first.

[pdurbin]

Specifically I would say that this cannot be MERGED until 5.14 is released.

We can certainly resolve merge conflicts ahead of time and generally keep this PR in a state that it will be ready to be reviewed, tested, and merged.

Also, the point about Payara is that we need to upgrade Payara for security reasons (Payara 5 is end of life per #8305). This Java upgrade can wait if necessary. We just thought we'd try to bundle a few platform upgrades together if there's time to get them all in.

[cmbz]

• Prioritizing Payara 6 release
• Sizing needed

[cmbz]

Sizing: Recommended as 33

[pdurbin]

I saw some merge conflicts and wanted to step through the upgrade myself anyway.

I'm closing this is favor of a new PR I just made:

• Upgrade to Java 17 #9764

That said, I'll definitely refer back to this PR as I work away. Here's where I learned we need to upgrade REST Assured.