Respect Content-Type header when rendering page, GraphQL improvements

NEW

• use Content-Type header to determine the Page format

Previously, it was required to explicitly provide the format in the URL to access a page with a different format than html, for example, app/views/pages/hello.json.liquid was accessible via https://example.com/hello.json, even if you made the request using the Content-Type: application/json header. Now, in such a scenario, we will try to load the page with the format json first, and if it's not available, we fall back to html for backwards compatibility.

IMPROVED

• error messages for various GraphQL errors related to invalid DB queries
• the graphql tag can now be closed using the {%- endgraphql -%} tag (with dashes). Previously, it was causing a Liquid error.

FIXED

• edge case scenarios related to using sort in GraphQL queries when related_models / related_users was used

pos-cli changes

pos-cli changelog is kept separately.