🤖 Refactor Celery Initialization and Database Setup Checks

[sentry-autofix]

👋 Hi there! This PR was automatically generated by Autofix 🤖

This fix was triggered by Rohan Agarwal

Fixes SEER-9P

This pull request includes significant changes to how the Celery application and database initialization are handled. In src/celery_app/app.py, the Celery initialization now connects the configuration setup to the worker's startup event instead of the on_configure event. A utility function _is_celery_worker() has been added to check if the current process is a Celery worker, ensuring that the bootup() function and periodic task setup only execute in a Celery context.

In src/seer/db.py, additional functions is_db_initialized() and mark_db_initialized() are introduced for checking and marking the database initialization state in the Flask application context. The initialize_database() function now checks if the database has already been initialized before proceeding, thereby preventing redundant setups and ensuring better state management within the application.

If you have any questions or feedback for the Sentry team about this fix, please email [email protected] with the Run ID: 1990.