access scope tweaks

[abrown-RV]

A few tweaks for how access scopes are validated.

• new $defs/access_scopes_enum to share the 4 st2138 access scopes
• $def/access_scope changed to anyOf access_scopes_enum or string (needs to be anyOf and not oneOf because strings in the enum also match string, breaking the ONE part of oneOf
• default_scope also uses the enum now.
• added uniqueItems to $defs/access_scopes (the top level list) since there is a comment saying they should be unique, may as well enforce.
• made slot, access_scope and default_scope all required in the device so these changes cannot be avoided by omitting.

Confirmed even with the anyOf the enum still is prompted in an ide:

[Copilot]

Pull request overview

This PR tightens and centralizes access-scope validation in the Catena device model JSON Schema by introducing a shared ST 2138 scope enum, enforcing uniqueness for the device’s access scope list, and making core access-scope-related fields mandatory at the top level.

Changes:

• Introduces $defs/access_scopes_enum to share the standard ST 2138 access scope values.
• Updates $defs/access_scope to allow either a standard enum value or an arbitrary string via anyOf, and updates default_scope to use the shared enum.
• Enforces uniqueItems: true on the device-level access_scopes array and makes slot, access_scopes, and default_scope required.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mejohnnaylor]

looks good. go ahead!