fix: add missing 'keys' subcommand to blobstream evm update commands

[Copilot]

• Rebase branch onto main (after base PR refactor(docs): bring back blobstream #2357 was squash-merged into main at 86f624d)
• Fix missing 'keys' subcommand in blobstream orchestrator evm update command at line 171
• Fix missing 'keys' subcommand in blobstream orchestrator evm update command at line 182
• Validate all commands in documentation are now consistent

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[gbarros]

@copilot can you rebase from main branch? The base branch for this PR has been squash-merged.

[Copilot]

@copilot can you rebase from main branch? The base branch for this PR has been squash-merged.

I've successfully rebased the branch onto main (commit 86f624d). However, the system doesn't allow force pushing.

Would you prefer me to:

1. Create a new PR with the rebased changes, or
2. Have you manually update the base branch of this PR to point to main?

The changes are ready - I just need the right approach to update the remote branch.

@copilot can you rebase from main branch? The base branch for this PR has been squash-merged.

Rebase completed successfully. The branch is now based on main (commit 86f624d, which contains the squash-merged PR #2357). The fix for the missing 'keys' subcommand is in commit 0a78d32.

The branch has diverged from the remote (ahead 3, behind 3) as expected after a rebase. To update the PR, you'll need to manually change the base branch to main on GitHub, or I can open a new PR with these changes. Which would you prefer?

[github-actions]

🚀 Preview Deployment

Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2361/