🚀 Feature: Optional DB foreign keys to avoid orphans

### 🔖 Feature description It would be nice if there were helper ways to avoid/control orphans: 1. Make optional the creation of DB Foreign Keys, when creating a realtionship in a collection. 2. Appwrite crud methods/requests have an optional param to check if relations are orphans, for example if I create/read/update a record, it can optionally check if the relational ids exists. These options should reduce the code developers must write (in functions) if avoiding orphans is a requirement. ### 🎤 Pitch When avoiding "orphan rows" is a requirement, checks can be done in functions, but these proposed features will simplify the creation of backend (one less thing to be worry about). ### 👀 Have you spent some time to check if this issue has been raised before? - [X] I checked and didn't find similar issue ### 🏢 Have you read the Code of Conduct? - [X] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)