Quote long 0x hex literals in GitHub workflow files to fix YAML parsing

[MontrealAI]

Motivation

• GitHub Actions rejected workflows due to long 0x... literals being parsed as YAML hex integers (overflow/invalid integer) and causing “Invalid workflow file” errors.
• These long hex values appear in many workflow env blocks (private keys / validator keys) and must be treated as strings.
• The intent is to make workflows syntactically valid without loosening checks or disabling jobs.
• Ensure CI manifests and companion workflow contexts remain unchanged in meaning while fixing YAML parsing.

Description

• Quoted long 0x... literals wherever they appeared in .github/workflows/* so YAML treats them as strings (e.g. changed 0xabc... → "0xabc...").
• Files updated: .github/workflows/ci.yml, .github/workflows/demo-asi-global.yml, .github/workflows/demo-asi-takeoff.yml, .github/workflows/demo-aurora.yml, .github/workflows/demo-zenith-hypernova.yml, .github/workflows/demo-zenith-sapience-celestial-archon.yml, .github/workflows/demo-zenith-sapience-initiative.yml, .github/workflows/demo-zenith-sapience-omnidominion.yml, and .github/workflows/demo-zenith-sapience-planetary-os.yml.
• No workflow semantics were changed beyond ensuring the hex values are YAML strings; CHAIN_ID and other numeric-looking values were left intact where already appropriate.
• Validated workflow YAML syntax locally using a small pyyaml parse check to prevent regressions.

Testing

• Ran a repository-wide YAML parse check with yaml.safe_load over .github/workflows/*.yml and the script reported YAML parse OK (success).
• Executed npm run ci:sync-contexts -- --check and it confirmed the required contexts are in sync (success).
• Executed npm run ci:verify-contexts and npm run ci:verify-companion-contexts and both reported successful verification of workflow display names and companion contexts (success).
• Executed npm run ci:verify-summary-needs and it confirmed the summary needs list covers all non-summary jobs (success).

---

Codex Task