Overhaul Fujifilm ASCOM driver

[Scdouglas1999]

Summary

• overhaul the ASCOM exposure lifecycle with repeated RAW polling, accurate progress, timed/T/bulb shutter selection, and working abort/stop paths
• correct Fujifilm SDK signatures, constants, and optional property calls; validate every native entry point against the bundled DLLs
• add X-Trans compatibility conversion, active-area cropping, rotated-RAW handling, and companion-frame filtering
• reference-count shared camera sessions and prevent stale timer/poll callbacks from contaminating later exposures
• synchronize and validate 18 camera configurations with the NINA Fujifilm Native Plugin catalog
• add cross-platform core tests, managed-driver compilation, interop verification, CI, release notes, and refreshed setup/documentation

Validation

• dotnet run --project tests/Fujicom.Core.Tests/Fujicom.Core.Tests.csproj --configuration Release — 8/8 checks passed
• dotnet msbuild Fuji/Fuji.csproj -t:Restore -p:BuildProjectReferences=false
• dotnet msbuild Fuji/Fuji.csproj -t:Build -p:Configuration=Release -p:Platform=AnyCPU -p:BuildProjectReferences=false — managed ASCOM driver compiled
• python3 build/verify-sdk-interop.py — 25 XAPI exports, 7 LibRaw exports, and 5 high-risk signature/constant contracts passed
• git diff --check — clean

Hardware-validation boundary

This environment cannot compile the x64 C++/CLI wrapper or exercise the proprietary USB protocol against a physical Fujifilm body. Before a 3.0 installer/release is cut, this should be built on Windows and smoke-tested with ASCOM Platform plus at least one GFX Bayer and one X-Trans camera. The PR is intentionally opened as a draft for that final validation.