feat(ai): add telemetry, error explanation, contract optimization, and security training

[dragoncode-01]

…

Implements four AI feature issues as a cohesive set under starforge ai:

• Usage telemetry (#482): per-call tracking of provider/model, tokens, cost, latency percentiles, and error rates, stored locally with an opt-out and ai telemetry show|cost|status|clear reporting commands.
• Error explanation (#511): ai explain-error classifies compilation, runtime, network, configuration, and deployment errors and returns plain- language explanations, root cause, fixes, and troubleshooting steps.
• Contract optimization (#497): ai optimize adds before/after gas-weight comparison, a diff view, and a public-function safety check before writing optimized output, gated behind confirmation.
• Security training (#576): ai security-training ships an offline lesson and quiz curriculum with per-topic progress tracking and personalized "what to study next" recommendations.

Also fixes several build breaks unrelated to these features but blocking compilation of this branch: missing UpgradeSimulationResult/AuthEntry types and a missing horizon::fetch_account_signers implementation from an earlier upgrade-command commit, a stray #[command(subcommand)] on the Ai CLI variant, a missing anyhow::Context import, and an async-openai 0.14 API mismatch (message construction, client type, response content handling) in the AI command module.

Closes #482
Closes #511
Closes #497
Closes #576

Description

Brief description of what this PR does and why.

Closes #(issue number)

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Changes Made

• Change 1
• Change 2
• Change 3

Testing

How has this been tested?

Describe the tests you ran and how to reproduce them.

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Test Coverage

Describe what scenarios have been tested:

• Happy path:
• Edge cases:
• Error handling:

Code Quality Checklist

• My code follows the style guidelines of this project (cargo fmt)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings (cargo clippy -- -D warnings)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The CI checks pass (format, clippy, tests)

Breaking Changes

• This PR introduces breaking changes

If checked, describe the breaking changes and migration path:

Documentation

• README.md updated (if applicable)
• No documentation changes needed

Screenshots (if applicable)

Add screenshots or GIFs for UI changes.

Additional Context

Add any other context about the PR here.

---