Rich Text Versioning optimizations [MAPS-137]

[joaquincasal]

Purpose

A customer is having an issue in which the dialog of the app is not displaying correctly due to a "response too big" error.

Approach

We've introduced some optimizations so requests made by the app have a smaller response size:

• Separate entries and assets referenced in the published and current field, so responses are smaller. This also speeds up the search that happens later in the createOptions method
• When fetching assets, use the select paramester to only retrieve the title, which is the only thing that gets used
• Add the include: 0 parameter when using entry.getPublished since by default the response includes an include array that is not used