Assumption of hard coded config

[leongross]

For this demo, we do rely on a configuration struct (config as code), that includes relevant components, such as, but not limited to:

• Downstream device definitions
• partitioning schemes for openprot itself
• cryptographic keys for signature verification

Status / remaining work

• Downstream device definitions — landed in fwmanager: Add device-table schema; declare a mock board in target/mock OpenPRoT/openprot#367 (device-table schema + mock board in target/mock/devices.rs)
• Partitioning scheme for openprot itself (active/recovery/golden partitions; relates to Active partition tracking #15)
• Cryptographic keys for signature verification (key format, algorithm, provisioning source; relates to Downstream firmware signature verification #4)
• Device tables for real hardware targets (mock board only so far — need AMD platform device list, reset lines, boot order)

PRs

• fwmanager: Add device-table schema; declare a mock board in target/mock OpenPRoT/openprot#367 (merged)
• fwmanager: Add per-device slot layout to the device-table schema OpenPRoT/openprot#394 (open)