fix(camera): complete the native CVS package transition

[rfrost-xyz]

Relates to omacom/omarchy#10948.

Linux 7.2 routed IPU camera discovery through CVS, but the packaged kernel leaves the native CVS driver disabled. The legacy DKMS driver does not register the required V4L2 endpoint, leaving IPU7 waiting for INTC10E1-0/port@1/endpoint@0 and OV08X40 unavailable.

This proposes a coordinated native CVS transition in the kernel and camera packages:

• Enable native CVS in linux-ptl 7.2.3.arch1-2. Add its missing ancillary autoselection default while preserving the upstream helper-menu placement and dependency bounds. Fail package preparation if olddefconfig drops the driver.
• Carry the existing firmware-owned sensor-power policy into the native driver specifically for Synaptics 06cb:0701 with Panther Lake INTC10E1. Preserve privacy ownership and behaviour on other devices.
• Release camera stack 1.0.6-1 with native-kernel exclusion for legacy CVS DKMS. The versioned source-directory change lets the existing package removal hook retire the old registration. Legacy kernels retain the legacy driver.
• Backport Intel's native-CVS HAL topology support, propagate negotiated formats to the bridge, report format failures and add the required bundled UAPI definitions. Preserve existing sensor configuration and direct-sensor support.

Validation at 2e00e40:

• Full kernel, headers and camera package builds pass in isolated edge containers.
• Real package transactions verify native CVS ownership after a combined upgrade, then restore the exact baseline packages and legacy DKMS registration on reversal. Camera-only upgrade/reversal also preserves legacy-kernel support.
• Full kernel configuration, 11 Kconfig dependency cases, HAL methods using bundled headers and nine power/privacy-policy cases pass. Regression checks fail against the corresponding original sources. These tests were run manually; the current CI workflow does not invoke them.

Ready for source review; hardware validation is required before merge. This is a proposed fix, not a confirmed camera repair. The affected daily-use laptop has not been upgraded to these candidate packages. A maintainer or affected-device tester is needed to validate boot, capture, privacy and suspend/resume. Container transactions exercise package/DKMS behaviour and initramfs generation, but not Limine/UEFI boot, actual camera frames, browser capture, privacy indication or suspend/resume. The logs include expected legacy-DKMS exclusion and container-only systemd, vconsole and unrelated header-only kernel warnings. The proposed Kconfig default and native power policy have not been accepted upstream or verified on the affected hardware.