[BUG] Memory allocation inefficiencies during agent initialization

[kyegomez]

[BUG] UUID generation overhead in agent initialization causing performance bottleneck

Description
Agent initialization uses UUID v4 generation for every agent, causing significant performance overhead due to cryptographic random number generation and string conversion operations.

Current Behavior

• Every agent generates a new UUID v4 during initialization
• UUID is immediately converted to string, requiring heap allocation
• Cryptographic random number generation adds latency per agent

Root Cause

// In AgentConfig::default()
let id = uuid::Uuid::new_v4().to_string();

Performance Impact

• Contributes to 187µs per agent initialization time
• Cryptographic operations are expensive for bulk initialization
• String conversion adds additional heap allocation overhead

Expected Behavior

• Fast ID generation suitable for bulk initialization scenarios
• Option to use sequential or simple IDs for performance-critical paths
• Maintain UUID compatibility for production use cases

Proposed Solutions

1. Use sequential numeric IDs for benchmarks/bulk operations
2. Implement UUID pool with pre-generated IDs
3. Add configuration option for ID generation strategy
4. Use faster non-cryptographic UUID algorithms for non-security contexts

Environment

• Component: AgentConfig initialization
• Performance impact: Medium (estimated 10-15% improvement potential)

Acceptance Criteria

• Implement alternative ID generation strategies
• Maintain backward compatibility with UUID format
• Reduce per-agent ID generation overhead by 60%+
• Add configuration option for ID strategy selection