Fix 5893 oauth deeplink multiple sessions

[rohankm]

What does this PR do?

The default OAuth URL is primarily utilized as a deep link on mobile applications to establish sessions. However, the current approach has a flaw as it sets the cookies on the appwrite domain. This presents an issue, particularly when two mobile apps are concurrently running on the same project, as one app's session might overwrite another's.

To rectify this, it is advisable not to include the cookies in the default success link. By doing so, a session will not be created on the browser end, enabling two apps for the same project to function independently without any session conflicts.

Test Plan

I have manually tested it with two different apps running on react native for the same project.

Related PRs and Issues

• The Oauth sessions from deep links expires on mobile when two different apps runs on the same project #5893

Checklist

• [yes] Have you read the Contributing Guidelines on issues?
• [no] If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?