Fix CLI Windows browser launch and bump console SDK

[ChiragAgg5k]

Summary

• Fix Windows CLI browser launch by avoiding cmd /c start and passing the URL directly to rundll32 url.dll,FileProtocolHandler.
• Bump @appwrite.io/console to ^15.1.1 and refresh CLI npm/bun lock templates.
• Add a regression test that verifies Windows browser launch preserves URLs containing spaces and cmd metacharacters.

Testing

• php example.php cli
• ./scripts/update-lockfiles.sh cli
• composer refactor:check
• composer lint-twig
• vendor/bin/phpunit tests/e2e/CLIBun13Test.php

Related Issue

• #XXXX

[greptile-apps]

Greptile Summary

This PR updates the CLI browser launch path on Windows and refreshes the console SDK dependency. The main changes are:

• Windows browser opening now uses rundll32 url.dll,FileProtocolHandler with the URL as a direct argument.
• CLI package and lock templates now depend on @appwrite.io/console ^15.1.1.
• The CLI auth tests now cover Windows URLs with spaces and command metacharacters.

Confidence Score: 5/5

The changes are narrowly scoped and covered by a regression test for the Windows URL handling behavior.

The updated browser-launch command avoids shell interpretation and the dependency bump is reflected consistently across package templates and lockfiles.

T-Rex Logs

What T-Rex did

• Compared the Windows browser launch logs; the base run used CMD to start the URL, while the head run used rundll32 with FileProtocolHandler to open the URL and set URL_ARG_EXACT to true.
• Compared the package manifests and lockfiles; the base state shows ^15.1.0 with npm and bun at 15.1.0, and the head state shows ^15.1.1 with npm and bun at 15.1.1, with consistency checks passing.

_{Ran code and verified through T-Rex}

_{Reviews (3): Last reviewed commit: "Fix Windows open browser test expectatio..." | Re-trigger Greptile}