feat: Add schema generation to GitHub Actions

[Leo10Gama]

Why is this change necessary?

With the new schema generation logic, we want to ensure that the script runs in such a way as to keep the schema up to date with the current changes.

How does it address the issue?

A new GitHub Actions workflow has been created to run the schema generation script once per weekday, check if the schema has been altered in any way, and if it has, open a PR to make the necessary changes.

What side effects does this change have?

At least once every weekday, if the generated schema is changed in any way, a PR will be raised to update it.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.