Create workflow to sync contracts via Git subtrees in client applications

[andrewtavis]

Terms

• [x] I have searched open and closed feature requests
• [x] I agree to follow Scribe-Data's Code of Conduct

Description

As discussed in https://github.com/scribe-org/Scribe-Android/issues/268, we need a way to assure that there's only one source of truth for Scribe client application contracts that will control data flows in the applications. The best way to do this would be to have the data contracts directory in the repo be this source of truth, with it further potentially being a subtree for directories with the contracts in the client applications. Whenever there's a change to the directory here, we would then trigger a workflow to open PRs to update the subtrees in the client applications :)

[!NOTE] We likely should make two different directories for contracts in the work here. One for Scribe keyboard applications and one for Scribe-Conjugate as the contracts for each will need to be different.

Contribution

Happy to discuss and work on the implementation here as needed 😊

[andrewtavis]

CC @angrezichatterbox and @axif0 for the discussion here :)