🐛 Bug Report: [Relationships] Child document permissions are ignored when linking through a reference

### 👟 Reproduction steps When creating / updating / reading both parent and child documents, user has to have permissions on both parent and child documents, but when linking the parent and child document through references, appwrite only checks if the user has permission on parent document. This could lead to security issue where user can link any child document without having necessary permissions on child document. For example, let's say we have two collections Posts (parent) and Groups (child). User can create a document in posts and link it to any private group with out having permission on that private group document. In other words, any user can create a post in any group. So the question is why appwrite has to treat linking a child document through reference any different than the nested syntax? ### 👍 Expected behavior User should be only able to link a child document to a parent only if they have read permission on child document. ### 👎 Actual Behavior User is able to link a child document to a parent even if they do not have read permission on child document. ### 🎲 Appwrite version Version 1.4.x ### 💻 Operating system MacOS ### 🧱 Your Environment _No response_ ### 👀 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)