chore: adapt to xbl.io response schema changes

[derklaro]

It seems like the xbl.io did some breaking changes to their response schema. It now almost always responds with status 200, carrying further information about a response in the body exclusively. All the data fields were moved into a "content" object which holds all the details and data of the upstream api response.

Example:

GET https://xbl.io/api/v2/account/2535449128108254343
{
    "content": {
        "code": 59,
        "StatusCode": 400,
        "source": "Profile",
        "description": "All Xuids in request are invalid. Xuids: 2526441928853513351",
        "traceInformation": null
    },
    "code": 400
}