Send response data in renderPage attribute

This code is hacky and undoubtedly needs a pair of eyes on it to find a better way.

Previously this data was sent in two places - "renderPage" and the class name of the entity that was sent.

Eg:

    {
      "renderPage": data here...
      "Collection_Timetable": same data here...
    }

This patch fixes that.

It also avoids a collision whereby login information - stored in `Object_User` - would clash with the response of an API call to `/rest/user`.