device-health-oracle: update link.health and device.health

[nikw9944]

Summary

• Add automatic health promotion for devices and links in provisioning states to the device-health-oracle component
• Implement efficient batched transactions (8 items per batch) to handle large numbers of simultaneous device/link additions while staying within Solana's default 200,000 compute unit budget
• Fix Go SDK serviceability state enums to match Rust implementation's numeric values (e.g., Deleting=3, Drained=5)
• Add required signer keypair configuration to execute onchain health state updates

Context

This implements the device-health-oracle portion of RFC12 (network provisioning). The oracle automatically promotes devices and links from provisioning states (DeviceProvisioning, LinkProvisioning, SoftDrained, HardDrained) to ready states without performing actual health checks, matching the current activator behavior.

The batching implementation processes health updates in groups of 8. Transaction wire cost per instruction is only ~9 bytes (accounts are deduplicated as 1-byte indices), so transaction size is not the bottleneck. The limiting factor is compute units: each instruction deserializes GlobalState (which contains variable-length allowlists) plus the device/link account, costing roughly 10,000-20,000 CUs per instruction. With Solana's default 200,000 CU budget, 8 instructions is a conservative limit.

The SDK enum fixes resolve a mismatch where Go used sequential iota values (0,1,2,3...) while Rust uses explicit numeric values with gaps (0,1,3,4,5...). This caused incorrect state interpretation and is now aligned across languages.

Testing Verification

• Device-health-oracle successfully processes devices in DeviceProvisioning and LinkProvisioning states during e2e tests
• Batched transactions complete successfully when processing multiple devices/links simultaneously
• Link onchain allocation test now correctly identifies Deleting status after SDK enum alignment
• Device-health-oracle container starts successfully with signer keypair mounted in e2e environment

[nikw9944]

Note that merging this to main will require deploying device-health-oracle to testnet/mainnet-beta before promoting this change to those environments.

[martinsander00]

updatePendingDeviceHealth/updatePendingLinkHealth update all devices, should we change the names? and is the behavior intended or do we want some filtering?