fix(api): encode query params in search and user lookup URLs

[deepak0x]

Fixes #1276

getSearchMessages builds URLs with template literals and drops user input straight into the query string without encoding. Search for hello & goodbye and the server gets searchText=hello because the & starts a new param. Search for #channel and searchText arrives empty because # is a URL fragment.

Same thing in getUserStatus, userInfo, and userData. Those are less likely to hit it since user IDs tend to be alphanumeric, but userData takes a username and usernames can have special characters.

Added encodeURIComponent() to all four.