Replace device roles with capabilities within Margo artifacts

[ajcraig]

Feature description

Goal: Rewrite sections that relied on Margo device roles, to be centered around device capabilities.

The device roles defined within Margo enabled the community to make progress towards our PR1 goals. However, as we continue to investigate additional use cases such as gateway functionality, these roles are becoming restrictive.

Provide adequate technical acceptance criteria(s) associated with this feature below:

• All sections referencing Device roles rewritten to focus on groups of functionality and configuration.
• These groups of functionality/configuration should roll up to represent a device "Capability".
  • This capability should be utlized within the artifact the device sends to the WFM during onboarding.
• Guidance towards how these changes impact the Margo Sandbox

Although not required, it is highly encouraged to provide feature use-cases below:

• Devices that support multiple deployment models
• Enable freedom for device and platform vendors to create unique offerings in the field while not restricting management capabilities via Margo.
• This feature will enable the gateway sup currently in progress LINK

Additional information

No response

[HAHermsen]

Our use case (#171) demonstrates why capabilities-based approach is critical:

Location-bound real-time workloads (EtherCAT, PROFINET) need to declare:

• "I'm bound to specific hardware"
• "Don't reshuffle me on network loss"
• "Start me on reboot regardless of control-plane connectivity"

Device roles can't express this granularity, but device capabilities can.