v1/viz: Stop returning the db_size_in_bytes value

[Algunenano]

Changes v1/viz requests to stop calculating (and returning) the db_size_in_bytes value, which requires a really expensive cartodb.CDB_UserDataSize call.

I'm not sure if anybody is using this value from this exact call, but that would be a bad dependency that should call the appropriate endpoint, not a random viz list. I think we could remove way more information that is currently output by the API, but I've limited the change to the one that causes performance issues.

Example of old owner output:

{"id":"f80dfdef-ea5c-498d-b98a-82362650d944","name":null,"last_name":null,"username":"dev2","email":"rmrodriguez+dev@cartodb.com","avatar_url":"/assets/unversioned/images/avatars/avatar_pacman_yellow.png","website":null,"description":null,"location":null,"twitter_username":null,"disqus_shortname":null,"available_for_hire":false,"base_url":"http://localhost:3000/user/dev2","google_maps_query_string":null,"quota_in_bytes":99999999999999999,"table_count":3396,"viewer":false,"role_display":"builder","org_admin":false,"public_visualization_count":3,"all_visualization_count":11,"org_user":false,"remove_logo":false,"db_size_in_bytes":3194740736}

After the change the db_size_in_bytes is gone:

{"id":"f80dfdef-ea5c-498d-b98a-82362650d944","name":null,"last_name":null,"username":"dev2","email":"rmrodriguez+dev@cartodb.com","avatar_url":"/assets/unversioned/images/avatars/avatar_pacman_yellow.png","website":null,"description":null,"location":null,"twitter_username":null,"disqus_shortname":null,"available_for_hire":false,"base_url":"http://localhost:3000/user/dev2","google_maps_query_string":null,"quota_in_bytes":99999999999999999,"table_count":3396,"viewer":false,"role_display":"builder","org_admin":false,"public_visualization_count":3,"all_visualization_count":11,"org_user":false,"remove_logo":false}

[gonzaloriestra]

LGTM! I can't think of any possible usage of that size from this endpoint... @alrocar @VictorVelarde any idea?

[VictorVelarde]

Sorry for being late on this. I don't know about any direct use of db_size_in_bytes from v1/viz.

What I can tell you is that there is a similar field returned by /api/v3/me and I'm not sure if that should be affected also by this change. We used to consume the second from the Profile page, to display some visual indicators on % used and available, but not anymore