chore: use zkaleido logging

[prajwolrg]

Description

zkaleido-logging is a separate crate that implements noop logging for ZkVm builds. This PR uses that directly instead of now redefining the logic again.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor
• New or updated tests
• Dependency update
• Security fix

Notes to Reviewers

Checklist

• I have performed a self-review of my code.
• I have commented my code where necessary.
• I have updated the documentation if needed.
• My changes do not introduce new warnings.
• I have added tests that prove my changes are effective or that my feature works.
• New and existing tests pass with my changes.

Related Issues

[github-actions]

Commit: da0a469
SP1 Execution Results

program	cycles	success
ASM STF	118,483,823	yes
Moho Recursive	11,586,718	yes

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[storopoli]

ACK 5e4ab68