### What happened

`install/hardware/apple/fix-suspend-nvme.sh` hardcodes the NVMe at PCI
`0000:01:00.0`:

```bash
NVME_DEVICE="/sys/bus/pci/devices/0000:01:00.0/d3cold_allowed"

if [[ -f $NVME_DEVICE ]]; then
  ...
  ExecStart=/bin/bash -c 'echo 0 > /sys/bus/pci/devices/0000\:01\:00.0/d3cold_allowed'
```

On MacBook models with discrete graphics that address is the dGPU, not the NVMe.
On a MacBookPro13,3:

```
$ lspci -s 01:00.0
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X]
$ lspci -s 02:00.0
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963
```

The guard `[[ -f $NVME_DEVICE ]]` passes because `d3cold_allowed` exists on any
PCI device, so the script reports success and enables the service. The result is
the opposite of what's intended on both counts:

```
$ cat /sys/bus/pci/devices/0000:01:00.0/d3cold_allowed   # Radeon Pro 460
0
$ cat /sys/bus/pci/devices/0000:02:00.0/d3cold_allowed   # NVMe
1
```

The discrete GPU is pinned out of D3cold — so it can't fully power down, costing
idle power and heat — while the NVMe the fix exists for is left untouched.

`MacBookPro13,3` is matched explicitly by the script's own regex
(`MacBookPro13,[123]`), and it's the model in that list most likely to have a
dGPU shifting the PCI numbering.

### What was expected

The service should target whichever PCI address the NVMe actually has.

### Steps to reproduce

1. Install Omarchy on a MacBook with discrete graphics (MacBookPro13,3 or 14,3).
2. `systemctl cat omarchy-nvme-suspend-fix.service` → points at `0000:01:00.0`.
3. `lspci -s 01:00.0` → the GPU, not the NVMe.

### Fix

Derive the address instead of hardcoding it, e.g.:

```bash
NVME_PCI=$(basename "$(readlink -f /sys/class/nvme/nvme0/device)")
```

which gives `0000:02:00.0` here and `0000:01:00.0` on the models the current
code was written against. Machines that already ran the old script also need
`d3cold_allowed` restored to `1` on the GPU, since the wrong setting persists in
the enabled unit.

Happy to open a PR if you'd like.

### System details

- Model: MacBookPro13,3 (Mac-A5C67F76ED83108C)
- Omarchy: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- GPU: Intel HD Graphics 530 + AMD Radeon Pro 460 (`01:00.0`)
- NVMe: Samsung SM961/PM961/SM963 (`02:00.0`)