pls don't close my pr github

Since we're no longer sending thetheme_preference inapi/v2/users responses, should this be labelled as a breaking API change?
Context:coder/coder-desktop-macos#91

@ethanndickson would it suffice to re-add the field in the /api/v2/users response but mark it as deprecated?

EDIT: this was already done as part of this PR, the only other change was addingomitempty.

I think the change is fine honestly, but if it's breaking our own Coder integration (desktop), it's possible it could break someone else's.
..In saying that, I doubt people are actively consumingtheme_preference. If it does break something, it's probably just because they expected the field to be present like I did on desktop.