[BUG] Conflicting scheduler config for all kernels

### Pre-flight checklist

- [x] I have searched existing issues and this is not a duplicate.
- [x] I have read the [Contributing Guidelines](https://github.com/CachyOS/linux-cachyos/blob/master/CONTRIBUTING.md).
- [x] I have verified the issue is reproducible with the latest available CachyOS kernel.

### Bug description

The bore scheduler was "disabled" 5 months ago https://github.com/CachyOS/linux-cachyos/commit/709f0cf3d9be2d3007d6a0d807d80eb304a203ad, but the package files do not accurately reflect that:

##### PKGBUILD
- https://github.com/CachyOS/linux-cachyos/blob/ff5ccc4fa26d5272d929fb9c1838593a6347ca10/linux-cachyos/PKGBUILD#L267 The comment should just state `BORE Scheduler`
- https://github.com/CachyOS/linux-cachyos/blob/ff5ccc4fa26d5272d929fb9c1838593a6347ca10/linux-cachyos/PKGBUILD#L327 SCHED_BORE is still being added to the config without the kernel patch being present
- https://github.com/CachyOS/linux-cachyos/blob/ff5ccc4fa26d5272d929fb9c1838593a6347ca10/linux-cachyos-deckify/PKGBUILD#L227 Not all variants have it disabled. If it was removed for a regression, should the others not be switched over too? This [commit](https://github.com/CachyOS/linux-cachyos/commit/fce577750ec855408ecdf31cf1bfed087db36b03) changed the description, but the scheduler is still bore

##### Hardening
The BORE scheduler is used when the scheduler is set to `hardened`
https://github.com/CachyOS/linux-cachyos/blob/ff5ccc4fa26d5272d929fb9c1838593a6347ca10/linux-cachyos/PKGBUILD#L267
Nowhere in the BORE repository does it state that it is better than EEVDF for a hardening. I reckon that a patched scheduler is less hardened than the kernel default. Is `hardened` in the BORE switch case because it used to be the default?

I presume most of this is tech debt/accidental, but I've had a very confusing afternoon trying to figure out the relationship (if any) between the variants and how they are updated.

### Expected behaviour

1. All documentation states the correct scheduler
2. BORE is removed from all variants as it was disabled because of a regression
3. The `hardened` Linux scheduler is used without other patches

### Actual behaviour

1. The system uses BORE when the docs say EEVDF
2. BORE is being used in some variants after it was stated it was removed because of regressions
3. Other scheduler patches are being used with the `hardened` Linux patches