🚀 Feature: granular function builds by branch

### 🔖 Feature description **As a** user with three projects with each project representing one environment (`development`, `staging` and, `production`) **I want** to avoid building all `Appwrite Functions` for every project **When** they share a single repository ### 🎤 Pitch #### The why In my use-case, I have a paid Appwrite account with three projects: - `claymemoirs-development` - `claymemoirs-staging` (admitdly this one is probably unnecessary, but hey, valid for the use-case explanation) - `claymemoirs-production` I incrementally synch these projects during release cycles, by doing something like the following steps: 1. Create a new function in `claymemoirs-development` project which considers the git production branch to be "development" branch; 2. Write some code and push changes directly to the `development` branch; 3. Test integrations with my project locally against the `development` project and maybe some mocked 3rd party SaaS. Example: a process is triggered and does what is expected when some new user is created; 4. If code works, then open a PR from development to `staging` where I am no longer use my local machine. 5. If code works, then open a PR from `staging` to `prodduction` where, finally, customers can enjoy some new features. I also use functions to keep databases in synch using a small NPM package I've created and published publicly [Appwrite Database Migration Tool](https://www.npmjs.com/package/@franciscokloganb/appwrite-database-migration-tool). #### The problem When I push code to the `development` branch directly, or when I open a PR from a seperate branch into `development`, **all my three projects rebuild all functions in the repository** (I have one repository with multiple entry points to avoid creating one repository per function, as that would make difficult to re-use some code snippets that I consider important and I prefer the mental model of keeping things close), even when each of these projects technically point at different …