fix: use correct path for token file deletion in clearSessionData and logOutSession

[Aitriq]

Summary

clearSessionData and logOutSession fail to delete token files from the tokens/ directory due to incorrect path construction. This causes orphaned sessions to persist in show-all-sessions responses even after session data has been cleared.

Bug

Both controllers use __dirname + '../../../tokens/${session}.data.json' to build the token file path. This has two issues:

1. String concatenation without separator — __dirname does not end with /, so the resulting path is malformed (e.g. /opt/wppconnect-server/dist/controller../../../tokens/...)
2. Wrong number of ../ — depending on whether the code runs from src/ or dist/, three levels up may not resolve to the project root

Meanwhile, FileTokenStore already uses the correct approach: path.resolve(process.cwd(), './tokens/').

Fix

Replace __dirname + '../../../tokens/...' with path.resolve(process.cwd(), 'tokens', ...) in both:

• src/controller/miscController.ts (clearSessionData)
• src/controller/sessionController.ts (logOutSession)

Also fix variable shadowing in clearSessionData where const path = config.customUserDataDir + session shadows the path import.

Impact

Without this fix, calling clear-session-data or logout-session removes the Chrome user data directory but leaves the token file on disk. On restart, show-all-sessions (via getAllTokens) still lists these ghost sessions and attempts to restore them — potentially spawning hundreds of unnecessary Chrome processes.

Tested on production with v2.9.0.

Test plan

1. Start a session → verify token file exists in tokens/
2. Call clear-session-data → verify token file is deleted
3. Call show-all-sessions → verify session no longer appears
4. Restart server → verify no orphaned Chrome processes spawn