feat: initialize creator keys from factory config

[nasirudeenbadirudeen87-cloud]

Summary

• add a typed deployment configuration for creator key factory calls
• validate creator handle, supply, wallet-cap, and curve inputs before deployment
• deploy, initialize, register, index, and emit the key in one transaction

Verification

• cargo check -p creator-keys-factory

Fixes #995

[drips-wave]

@nasirudeenbadirudeen87-cloud Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[nasirudeenbadirudeen87-cloud]

@accesslayerorg @nasirudeenbadirudeen87-cloud The atomic creator-key deployment path is complete in commit b75c82c11bdd2324b8010b0ae9deb0ef14557755. It validates the creator handle, supply cap, wallet cap, and curve preset before deploying, initializes the child contract, records creator-ordered registry entries, and emits the deployment event. Verification: cargo check -p creator-keys-factory passed. The PR references Fixes #995. Please review and merge when CI is green.

[nasirudeenbadirudeen87-cloud]

The CI failure was only Rust formatting in creator-keys-factory/src/lib.rs. I formatted the file and pushed commit d8b1ddb to fix/issue-995; please rerun the verification workflow.

[nasirudeenbadirudeen87-cloud]

The formatting fix is pushed as d8b1ddb. The latest verification check is still failing, so this is no longer a cargo-fmt-only issue; please inspect the fresh verification log and rerun after addressing the remaining repository check failure.

[nasirudeenbadirudeen87-cloud]

The remaining verification failure was Clippy’s len_zero lint on config.handle.len() == 0. Replaced it with config.handle.is_empty() and pushed 0f01968. Please rerun CI.