account for timezone with java.time types in DateTimeConverter

[codylerum]

closes #5622

[codylerum]

@BalusC I'm getting a test failure here for some tests added for issue 5541

What what I'm seeing tough, since those converters are not defining a timezone they should default to GMT, unless the intrepetion is different for the java.time types, but I'm not finding that.

https://jakarta.ee/specifications/platform/10/apidocs/jakarta/faces/convert/datetimeconverter

Error:  Failures: 
Error:    Issue5541IT.testValidZonedDateTime:329 Multiple Failures (1 failure)
	org.opentest4j.AssertionFailedError: expected: <2024-06-30 12 uur 34 min +0130> but was: <2024-06-30 11 uur 04 min Z>
Error:    Issue5541IT.testValidZonedDateTimeBce:343 Multiple Failures (1 failure)
	org.opentest4j.AssertionFailedError: expected: <2024-06-30 12 uur 34 min +0130> but was: <2024-06-30 11 uur 04 min Z>
Error:    Issue5541IT.testValidZonedDateTimeBceNegative:357 Multiple Failures (1 failure)
	org.opentest4j.AssertionFailedError: expected: <-2024-06-30 12 uur 34 min +0130> but was: <-2024-06-30 11 uur 04 min Z>

Or is timeZone just not an honored attribute with zoneDateTime with the assumption is that the correct zone is already applied to the value?

[codylerum]

Looks like this is by design.

https://stackoverflow.com/questions/34883270/how-to-use-java-time-zoneddatetime-localdatetime-in-pcalendar#:~:text=Dealing%20with%20ZonedDateTime%20in%20JSF,explained%20in%20%231%20here%20above.