TLS improvements

[lucian-cm]

• Fixed defect with Undertow's TLS truststore and TLS keystore sharing the same password
• Undertow's TLS default keystore type is read from javax.net.ssl.keyStoreType if valid, otherwise it is PKCS12 (previously it was hardcoded to JKS)
• Undertow's TLS default truststore type is read from javax.net.ssl.trustStoreType system property if valid, otherwise it is JKS (previously it was hardcoded to JKS)
• Using latest TLS protocol TLSv1.3 for Undertow's HTTPS listener (previously it was not guaranteed to be TLSv1.3)
• Refactored some of the TLS handling logic

[lucian-cm]

@lvca, this PR is in relation to #775
Please take a look when you can.

[lvca]

Hi @lucian-cm, thanks, for checking it asap. Did you install pre-commit? https://github.com/ArcadeData/arcadedb/blob/main/CONTRIBUTING.md#pre-commit

[lucian-cm]

Hi @lucian-cm, thanks, for checking it asap. Did you install pre-commit? https://github.com/ArcadeData/arcadedb/blob/main/CONTRIBUTING.md#pre-commit

Thanks @lvca for your timely reply. I forgot to add the pre-commit checker before. I added it now and did not find anything to fix. It appears that the following tests are failing, which I believe are not related to my changes.

Results:
2023-02-12T21:50:59.8062567Z [INFO]
2023-02-12T21:50:59.8069175Z [ERROR] Failures:
2023-02-12T21:50:59.8077961Z [ERROR] DateTest.testInstant:392 expected: <2023-02-12T21:21:20.963787Z> but was: <2023-02-12T21:21:20.963787900Z>
2023-02-12T21:50:59.8078476Z [ERROR] DateTest.testSQLMath:449 expected: but was:
2023-02-12T21:50:59.8079213Z [ERROR] DateTest.testZonedDateTime:343 expected: but was:
2023-02-12T21:50:59.8079570Z [ERROR] Errors:
2023-02-12T21:50:59.8125883Z [ERROR] UpdateStatementExecutionTest.testLocalDateTimeUpsertWithIndex:892->lambda$testLocalDateTimeUpsertWithIndex$1:894 � DuplicatedKey Duplicated key [2023-02-12T21:48:59.484061, 2023-02-12T21:48:59.484061] found on index 'Product_1_25
80549119200' already assigned to record #9:0

Second test: I saw the problem is the fact that the saved value for date1 is less than the original date1, such that that the test has a wrong expected value to include the saved value of date1
date1 = 2023-02-13T10:33:26.869755500
date2 = 2023-02-13T10:33:27.869755500
result contains just the right side date, that is 2023-02-13T10:33:27.869755

a fix would be

[lvca]

Thanks @lucian-cm, merged!

[lucian-cm]

@lvca, thank you 👍 !