omarchy-hw-nvidia-without-gsp misclassifies Turing-based MX cards (e.g. MX550) as no-GSP, causing driver conflict with Steam install

[AndresSM415]

`omarchy-hw-nvidia-without-gsp` matches GPU names against `MX *[0-9]+` unconditionally, assuming all "MX" branded cards are pre-Turing (Maxwell/Pascal/Volta, no GSP firmware):

```bash

bin/omarchy-hw-nvidia-without-gsp

lspci | grep -i 'nvidia' | grep -qE "GTX (9[0-9]{2}|10[0-9]{2})|GT 10[0-9]{2}|Quadro [PM][0-9]{3,4}|Quadro GV100|MX *[0-9]+|Titan (X|Xp|V)|Tesla V100"
```

But NVIDIA continued the "MX" naming into the Turing generation (e.g. MX450, MX550, MX570 are `TU117`/`TU117M` chips — same generation as GTX 16xx, which `omarchy-hw-nvidia-gsp` does match). On a laptop with an MX550, this causes:

1. `omarchy-hw-nvidia-without-gsp` to incorrectly return true
2. `omarchy-install-gaming-gpu-lib32` (invoked during Steam install) to try installing `lib32-nvidia-580xx-utils`
3. A pacman conflict, since the correct mainline `lib32-nvidia-utils` was already installed (matching the correctly-detected mainline `nvidia-utils` driver from initial GPU setup)

Repro:
```
$ lspci | grep -i vga
02:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)

$ omarchy-hw-nvidia-gsp; echo $?
1
$ omarchy-hw-nvidia-without-gsp; echo $?
0
```

Suggested fix: exclude Turing-generation MX cards from the no-GSP pattern, e.g. change `MX *[0-9]+` to only match pre-Turing models (`MX1[0-9]{2}\b|MX2[0-9]{2}\b|MX3[0-9]{2}\b`, i.e. MX110–MX350), and/or add `MX[4-9][0-9]{2}` to the GSP-detector pattern in `omarchy-hw-nvidia-gsp`.