🚀 Enhancement: Introduce a way to use the user session without relying on client services in server sdks.

### 🔖 Enhancement description I was asked to post this as a feature request in Discord. At the moment, when I try to disable the client services from my Appwrite Cloud dashboard, I can no longer perform tasks as a user using their session cookie. The whole reason for going with a server SDK is to have more control over what comes in and out of my Appwrite instance. If I'm going to have the client side open regardless, then what's the point of server SDKs? I'm specifically referring to the Account service. ### 🎤 Pitch If the client side sdk needs to be active regardless, then all the logic I made in my server side to create a user for example is useless, because someone can create a user using the REST API with the project ID only. I'm not really sure what the best way to approach this is, as I'm not very familiar with Appwrite or Node.js. However, I suggest introducing a way to use the user session in server SDKs without relying on the client SDK. ### 👀 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)