Plugging in Honeycomb Alpha causes AntimicroX to instantly crash (0xc0000005)

### Is there an existing issue for this?

- [x] I searched the existing issues and did not find anything similar.

### Current Behavior

AntiMicroX crashes during startup whenever my Honeycomb Alpha Flight Controls is connected.

The behaviour is consistently reproducible:

Honeycomb Alpha connected -> AntiMicroX crashes during startup.
Honeycomb Alpha disconnected -> AntiMicroX starts and works normally.
Reconnect the Alpha -> it crashes instantaneously.

The Alpha itself appears to be detected successfully before the crash. The debug log reports it as:

Name: Alpha Flight Controls
Game Controller: No
\# of RawAxes: 2
\# of Axes: 2
\# of RawButtons: 35
\# of Buttons: 35
\# of Hats: 1

Windows Event Viewer reports the crash as:

Faulting application name: antimicrox.exe
Faulting module name: antimicrox.exe
Exception code: 0xc0000005
Fault offset: 0x0000000000112460

The issue originally occurred on an older AntiMicroX version as well. I updated to 3.6.1 but the problem persists.

### Expected Behavior

AntiMicroX should start normally with the Honeycomb Alpha connected and allow it to be used/mapped in the same way as my other attached joystick devices.

### Steps To Reproduce

1. Connect a Honeycomb Alpha Flight Controls.
2. Launch AntiMicroX.
3. AntiMicroX detects/initialises the attached controllers.
4. AntiMicroX crashes with a 0xc0000005 access violation.

To confirm the device dependency:

1. Disconnect the Honeycomb Alpha.
2. Launch AntiMicroX.
3. AntiMicroX launches successfully.
4. Close AntiMicroX.
5. Reconnect the Honeycomb Alpha.
6. Launch AntiMicroX again.
7. AntiMicroX crashes again.

(plus as mentioned before, with AntimicroX running, plugging in the Alpha causes an instant crash)

### Environment

```markdown
Program Version 3.6.1
Compiled from packaging: GitHub Windows Release
Built Against SDL 2.32.10
Running With SDL 2.32.10
Using Qt 6.10.3
Using Event Handler: SendInput
Host OS: windows Version: 11 Architecture: x86_64
```

### Anything else?

Other controllers attached to the system include:

Honeycomb Bravo Throttle Quadrant
VPC Rudder Pedals
R-VPC Stick MT-50CM2

These do not appear to cause the problem. AntiMicroX starts correctly with those devices attached as long as the Honeycomb Alpha is disconnected.

My normal profile is intentionally shared across several controllers. Its main purpose is to map PTT buttons on different physical devices to the same keyboard key (0x7C) for vPilot, which only supports a single joystick PTT binding.

Initially I suspected the existing profile may have become corrupt. However, I have since created a new profile from scratch and reproduced the same crash, so this does not appear to be limited to corruption of the original profile.

Some command-line testing was also performed:

`antimicrox.exe --version`

works normally.

`antimicrox.exe --list`

returns without crashing.

Normal application startup crashes with the Alpha connected. I also tested:

```
antimicrox.exe --tray
antimicrox.exe --no-tray
antimicrox.exe --hidden
```

and these also crash.

The debug log shows the Honeycomb Alpha being successfully enumerated before the crash. During profile initialisation it reaches:

> Change joystick "Alpha Flight Controls" profile to:
> "C:/Users/.../Documents/antimicroX/msfs.joystick.amgp"

and begins creating the controller's button objects before the application terminates.

I am attaching a ZIP containing:

- Full debug log from the crashing run
- Original profile
- Newly-created profile which also reproduces the issue

[antimicrox-honeycomb-alpha-crash-repro.zip](https://github.com/user-attachments/files/31921635/antimicrox-honeycomb-alpha-crash-repro.zip)