Upgraded dependencies, pinned SHAs, bump node to 24, run on ubuntu:latest

[db-ks]

Summary

• action.yml was using node20 as the JavaScript runtime
• GitHub Actions will force Node.js 24 as the default starting June 2nd, 2026, and Node.js 20 will be removed from runners on September 16th, 2026
• Updated using: 'node20' → using: 'node24'

The index.js uses only @actions/core, @actions/exec, @actions/io, and @actions/tool-cache which are all Node-version agnostic — no rebuild required.

Test workflow changes

• Bumped package.json version to 1.1.0
• Replaced deprecated ubuntu-20.04 runner with ubuntu-24.04 across all jobs — pinned to a specific LTS label rather than ubuntu-latest, which silently moves to the next LTS when GitHub rolls out a migration (over 1–2 months). GitHub-hosted runners have no SHA equivalent; the versioned label (e.g. ubuntu-24.04) is the closest equivalent to a pin.
• Pinned actions/checkout to SHA de0fac2e (v6.0.2)

OpenTAP bumped from 9.17.0 to 9.32.3 in the Linux jobs:
The old version 9.17.0 triggered a resolver bug where Demonstration:any resolves to 9.1.0, which depends on WPF Controls ^9.31.0-rc.2+c39a4f1f. That package is published as AnyCPU only, and the OpenTAP resolver in 9.17.0 incorrectly fails to match it against x64 Linux (exit code 33). This bug is fixed in recent versions of OpenTAP, so upgrading to 9.32.3 resolves it without needing to pin any packages.

Container image bumped from dotnet/sdk:8.0 to dotnet/sdk:9.0:
OpenTAP switched from .NET 6 to .NET 9 between versions 9.28.3 and 9.29.0 (skipping .NET 8 entirely). Running OpenTAP 9.32.3 inside the dotnet/sdk:8.0 container fails with exit code 150 (.NET 9.0.0 runtime not found). Updating the container to dotnet/sdk:9.0 aligns it with OpenTAP's current runtime requirement.

[rmadsen-ks]

Great stuff!