[Half-Shot]

3 common things we do in modules that probably should just get their own API. Unsure whether we should slap some warnings on these that they may break when multi-account comes in?

Removed the access token because it was controversial . Given the userId is already exposed as a watchable under Profile, I've cheekily included deviceId too rather than adding it under it's own thing.

Checklist

• I have read through review guidelines and CONTRIBUTING.md.
• I have linked the PR to an issue that describes what needs changing.
• I have written tests for new code (and old code if feasible).
• I have ensured new or updated public/exported symbols have accurate TSDoc documentation.
• I have confirmed linter and other CI checks pass.
• I have have included screenshots if what the user sees will change
• I have licensed the changes to Element by completing the Contributor License Agreement (CLA)
• I will no longer force push to this branch

AI assistance

• I used AI tools to help create this PR.

[t3chguy]

I think this is a bad idea. Token TTL default in MAS is 5 minutes. Which makes it rather likely that a token you read ends up expiring rather soon and you have to handle refresh. Your proposed API returns strings, not Watchables, and making all Modules respect token refresh would be spurious additional work which could be done on this side of the fence with a better API.