Refactor track lifecycle for better code organization (post-MVP)

[jonnyspicer]

Overview

Improve track management code organization by separating lifecycle components.

Priority Revision

DOWNGRADED from MVP Critical → Post-MVP Enhancement

Reason: The current Stone Soup integration already provides working track lifecycle management. This is code organization, not functionality.

Current State

• Stone Soup MultiTargetTracker handles track lifecycle effectively
• All functionality is working in StoneSoupTracker.py
• Recent code review already improved organization

Target State (Post-MVP)

• Better code organization with separated components
• Improved testability of individual lifecycle components
• Enhanced maintainability

Dependencies

• BLOCKED by Implement RadarOnlyAssociator for pure radar tracking #20 - Need radar-only operation working first
• Should be completed after core MVP functionality is proven

Benefits

• Better code organization and maintainability
• Easier testing of individual components
• Foundation for future enhancements

MVP Reality Check

The system already has working track lifecycle management via Stone Soup. The MVP priority is getting radar-only operation working, not reorganizing code that already works.

Note: This is a code quality improvement, not a functionality gap. MVP should focus on capability gaps first.