GitHub Action may create commits that remove all existing definitions

[lyqht]

Context

1. Users have reported that rarely, the GitHub Action bot has created commits that remove all the existing definitions, and this is due to the fact that there are rare times where the Supabase OpenSpecs API endpoint does not return correctly or that the OpenAPI Typescript API somehow fails to parse the result as intended.
2. Shortly after, the bot would make another commit to repopulate the previous definitions if the endpoint responds correctly afterwards.

This is not ideal, hence, there are a few tasks that can be embarked on:

• Check that the updated definitions file does not have an empty definitions section #2
  • GitHub Action should check that the updated database types file does not have an empty definitions section before making the commit for the result returned by the OpenAPI Typescript API.
• Option to create PRs instead of making direct commits to master #3
  • GitHub Action should have an option to create new branch + PR with the applied changes instead of committing directly to master, so user can see whether they are the right changes before choosing to merge to their desired branch.