Change profiles and kink retrieval to the JSON API

[aliciasprig]

The current method of using "PRO" and "KIN" to retrieve profile and kink data directly from the server needs to be depreciated, and replaced with the JSON API https://wiki.f-list.net/Json_endpoints which should be able to do the same and more.

Some thoughts on implementation details (actual implementation need not follow this):

The stub class "FCharacterProfile" should used to store profile data and to possibly perform JSON requests.

The "FServer" class should keep a list/cache of all viewed profiles. "FCharacterProfile" instances should probably keep a reference to the "FServer" instance as the need access to a valid account ticket to retrieve data by the JSON API.

The character profile dialog class should fetch new or cached profiles from the "FServer" instance and receive update notifications from the "FCharacterProfile" instance as data is retrieved.

[kythyria]

This would be a more sensible proposal if the current version of the API didn't default to refusing to give that information AT ALL: Not only do you need a ticket, but the character in question needs to belong to an account that has API access enabled.

I'm working on making a trivial wrapper for the API (it does little more than hide the JSON and hide the details of making HTTP requests) as part of revamping the login stuff; it should absorb the change to the v2 API fairly seamlessly.