Vibhav dev to develop

[VibhavSetlur]

This pull request introduces substantial improvements and new features to TableScanner, focusing on enhanced configuration, advanced database schema support, improved documentation, and expanded API response models. The changes include new environment variables for AI provider configuration, a comprehensive database schema for configuration management, improved exception handling, and significant updates to the documentation and API models for clarity and completeness.

Key changes:

Configuration and Environment

• Added extensive AI provider configuration options to .env.example, supporting multiple providers and fallback chains for automatic config generation.
• Introduced new configuration constants in app/config_constants.py for limits, cache, timeouts, and API versioning.
• Added new settings in app/config.py for KBase environment and timeout parameters, improving deployment flexibility and robustness.

Database Schema and Persistence

• Created a detailed schema in app/db/schema.sql to support a full configuration control plane, including config records with lifecycle states, audit logs, user overrides, version history, and test results.
• Added module-level documentation to app/db/__init__.py for clarity on the database module's purpose.

API Models and Error Handling

• Expanded API response models in app/models.py to include additional metadata such as object_type, config fingerprints, schema info, and database statistics, and removed legacy pangenome fields for clarity. [1] [2] [3]
• Introduced a custom exceptions module in app/exceptions.py for more granular error handling, including errors for missing tables, columns, filters, and database access issues.

Documentation and Developer Experience

• Completely overhauled README.md to provide clearer feature descriptions, quick start instructions, API usage examples, project structure, configuration, performance notes, and testing guidelines.
• Updated the FastAPI app description in app/main.py to reflect new features and capabilities, and adjusted CORS middleware for improved security defaults. [1] [2]
• Minor code hygiene improvements, such as import ordering and docstrings. [1] [2]

These changes collectively make TableScanner more robust, configurable, and user-friendly, while laying the groundwork for advanced configuration management and future extensibility.