Fix Pi 5 driver selection crash when only libgpiod.so.3 is installed

[Copilot]

The RaspberryPi5 case in GetBestDriverForBoardOnLinux() hardcodes LibGpiodDriver.GetAvailableChips() (V1 ABI, requires libgpiod.so.2), which crashes on recent Pi OS images that only ship libgpiod.so.3. Meanwhile, unmapped Pi 5 revisions fall through to UnixDriver.Create() which handles this gracefully — so rev 1.0 crashes but rev 1.1 works.

Changes

• GpioController.cs: Pi 5 case now uses GpioDriver.TryCreate() to try LibGpiodDriver (V1) first, then fall back to LibGpiodV2Driver (V2 ABI), reusing the same common function already used by UnixDriver.Create(). A small CreatePi5Driver helper finds the RP1 chip (54 lines) and creates the driver via a factory delegate.
• RaspberryBoardInfo.cs: Added firmware code 0x4171 (Pi 5 rev 1.1) to the RaspberryPi5 mapping so it gets proper Pi 5 driver selection instead of falling through to Unknown

// Before: crashes if libgpiod.so.2 is missing
var chips = LibGpiodDriver.GetAvailableChips();

// After: uses GpioDriver.TryCreate() to try V1, then V2
if (GpioDriver.TryCreate(() => CreatePi5Driver(LibGpiodDriver.GetAvailableChips(), id => new LibGpiodDriver(id)), out GpioDriver? pi5Driver))
{
    return pi5Driver;
}

if (GpioDriver.TryCreate(() => CreatePi5Driver(LibGpiodV2Driver.GetAvailableChips(), id => new LibGpiodV2Driver(id)), out pi5Driver))
{
    return pi5Driver;
}

[pgrawehr]

@copilot Instead of duplicating the logic of GpioDriver.Create() try to use a common function.

[Copilot]

@copilot Instead of duplicating the logic of GpioDriver.Create() try to use a common function.

Refactored in d2c526b to use GpioDriver.TryCreate() with a small CreatePi5Driver helper, matching the same pattern as UnixDriver.Create(). The manual try/catch blocks are gone.