Modify/create a flow that will update the records on the DB after a meeting is created

This will avoid that a meeting doesn't get saved in the scheduler DB even though an Outlook and GH issue was created

Start by tracing the meeting-creation flow and identifying where the scheduler database record is written relative to the Outlook and GitHub issue creation mentioned here. Confirm the expected behavior with maintainers, then define done as ensuring the scheduler record is updated when a meeting and its external records are created.

Written by the indexing model from the issue text.