feat: extract lightweight serialization component from clarity crate

[parsaaba]

Fixes #6236

Problem:

• The clarity crate included the full Clarity VM with heavy dependencies like rusqlite
• Downstream crates needed to compile the entire VM just to serialize/deserialize Clarity values
• This made it difficult to build lightweight applications that only needed serialization

Solution:

• Created new clarity-serialization crate with minimal dependencies
• Extracted core serialization types and traits from the main clarity crate
• Maintained full API compatibility for existing code

Changes:

• Add new clarity-serialization crate with lightweight dependencies
• Extract Value enum and all supporting types (TupleData, ListData, etc.)
• Extract ClaritySerializable/ClarityDeserializable traits and serialization logic
• Extract core representations (ClarityName, ContractName, QualifiedContractIdentifier)
• Add comprehensive error handling and validation
• Update main clarity crate to depend on and re-export from clarity-serialization
• Add workspace member for new crate
• Include working example demonstrating usage

Benefits:

• Downstream applications can serialize Clarity values without heavy VM dependencies
• Faster compilation for lightweight use cases
• Better separation of concerns between serialization and VM logic
• Maintains backwards compatibility

Description

Applicable issues

• fixes #

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[CLAassistant]

All committers have signed the CLA.