Introduce provider-aware chart processing foundation

[bkielczewski]

Summary

This PR introduces a provider-aware foundation for chart processing while preserving the existing FAA behavior and public API shape. faa_tpp remains the only implemented provider in this PR. The purpose here is to make the current ingestion/retrieval pipeline extensible enough to support additional providers, such as UK AIP, in follow-up work.

Changes

• Added internal provider routing across AIRAC state, repositories, and SNS messaging
• Made airport and AIRAC storage keys provider-aware
• Introduced a provider registry in the chart processor
• Wrapped current FAA behavior in a faa_tpp provider
• Let providers define expected processing jobs
• Kept chart API routes unchanged; collectors now resolve across registered providers internally
• Removed the implicit USA default from AirportData; FAA processing now sets country explicitly

Compatibility

• Existing API routes remain unchanged
• Existing FAA behavior is preserved
• Legacy FAA storage keys remain readable