Switch deprecated startup events to lifespan events

[alyssadai]

The @app.on_event("startup") syntax seems to be deprecated: https://fastapi.tiangolo.com/advanced/events/#alternative-events-deprecated and replaced by https://fastapi.tiangolo.com/advanced/events/#lifespan

We should look into updating the startup checks for defined credentials and allowed origins to follow this new syntax.

Originally posted by @surchs in #151 (comment)

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[samadpls]

Hi @alyssadai, Can i take this issue? 😋

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[KhushiRajurkar]

Hello @alyssadai, thank you for your detailed response and guidance!

I’ve reviewed PR #287 and understand that the primary task involves refactoring the lifespan event to align with the latest changes in main.py. I’ve also noted the differences between the implementation in PR #287 and the current version of main.py.

My plan is to:

1. Update the lifespan function to incorporate all the startup and shutdown logic from the current main.py file.
2. Ensure compatibility with any new features or changes introduced in the main.py since PR [MNT] Switched to lifespan events #287.
3. Test the implementation thoroughly to confirm that it works as intended.

I would like to begin working on this and contribute a PR to resolve issue #152. Could you please assign the issue to me?

Thank you!

[alyssadai]

Hi @KhushiRajurkar, thanks for your interest in contributing. I've assigned you to the issue.