Quote NO in zubpm Yamale schema to fix example-config validation

[Copilot]

The Validate Example Configs job failed on the zubpm example because the schema key NO was parsed as a YAML boolean token, causing Yamale to look for environment.False. This change makes the schema key explicit so the example validates as intended.

• Root cause

  • In roles/device_roles/zubpm/schema.yml, unquoted NO was interpreted as boolean-like YAML syntax instead of a literal field name.

• Change

  • Updated the zubpm role schema to quote the field name:
    • NO: int() → "NO": int()

• Impact

  • Aligns schema key parsing with the existing example config structure.
  • Removes the zubpm-specific failure in the example-schema validation workflow.

environment:
  IOCNAME: str()
  "NO": int()
  PSC: str()