Crash loading fonts

### Please provide a brief summary of the bug

We've had over 100 reports from users experiencing this crash with our application (Screaming Frog [SEO Spider](https://www.screamingfrog.co.uk/seo-spider/)). In every instance of this crash the user has an Indian Locale and/or Timezone.

We've been lucky enough to have 1 of the users experiencing this issue work with us (we are unable to reproduce this ourselves) to help us produce a minimal program that reproduces the issue.

The crash when using the Adoptium version is: [hs_err_pid6824.log](https://github.com/adoptium/adoptium-support/files/9784585/hs_err_pid6824.log).

The Oracle version works correctly and produces:


What we know:
- This happens only to users with a an Indian Locale and/or Timezone
- This doesn't happen to all users with Indian Locale and/or Timezone
- This happens using the JDK from Adoptium, but not from Oracle.
- Removing the line `UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());` prevents the crash from happening.

### Please provide steps to reproduce where possible

Please see https://github.com/screamingfrog/adoptium-font-crash for a standalone repo that reproduces this issue.

There are two workflows - one that produces a version that compiles and run with the JDK/JRE from Adoptium, and one that does the same bug with Oracle. Both are using JDK 17.0.4.

Steps to reproduce are:

1) Download the build (Adoptium or Oracle from the [first release](https://github.com/screamingfrog/adoptium-font-crash/releases/tag/v1.0.0))
2) Extract the zip which will produce another zip called `adoptium-font-crash-1.0-SNAPSHOT-distribution.zip`
3) Extract this zip.
4) Move into the folder `adoptium-font-crash-1.0-SNAPSHOT`
5) Double click the file `run_me_windows.bat`

### Expected Results

An app like this appears


### Actual Results

It crashes like this [hs_err_pid6824.log](https://github.com/adoptium/adoptium-support/files/9784762/hs_err_pid6824.log)

### What Java Version are you using?

Java: Vendor 'Eclipse Adoptium' URL 'https://adoptium.net/' Version '17.0.4.1' Home 'C:\Users\Administrator\Documents\adoptium-font-crash-1.0-SNAPSHOT-distribution\adoptium-font-crash-1.0-SNAPSHOT\jre'

### What is your operating system and platform?

Platform: Name 'Windows 11' Version '10.0' Arch 'amd64'

### How did you install Java?

See `windows-adoptium.yml` workflow - I believe the zip, then the jre is produced using `jlink`.

### Did it work before?

```shell
Unknown.
```

### Did you test with other Java versions?

```shell
Yes, Oracle JDK, and that works.
```

### Relevant log output

```shell
Log is too long to copy in: There was an error creating your issue: body is too long (maximum is 65536 characters).
```

Start with the standalone adoptium-font-crash repository, the windows-adoptium.yml workflow, and run_me_windows.bat; reproduce the crash using the Adoptium and Oracle JDK 17.0.4 builds. Compare the supplied hs_err_pid6824.log files and the behavior with UIManager.setLookAndFeel removed. Done means the Adoptium build no longer crashes while loading the application under the affected locale or timezone conditions.

Written by the indexing model from the issue text.