Issue Summary

-User report that the API v2 page properties is not returning JSON data

Steps to Reproduce

1. An automatic page was created when the user created a new space, this was due to an experiment that is now closed.
2. When the automatic page gets created a Unicode emoji gets created on this new page and that is causing the API not to return JSON data correctly

     },
               "value":⭐️,
               "key": "emoji-title-draft",
               "id": "196823"
   

   Expected Results

• The API should return only in JSON format

  },
              "value": "2b50",
              "key": "emoji-title-draft",
              "id": "7766037"
  

  Actual Results

-Unicode emojis are not being detected by the API, returning this

  },
            "value":⭐️,
            "key": "emoji-title-draft",
            "id": "196823"

Workaround

• Since the experiment is now closed, new pages shouldn't have this problem, but all the automatic pages created when the experiment was active will present this issue.
• To fix the existing pages, one can replace the default emoji with another one from a standard set of Confluence emojis using this guide: https://support.atlassian.com/confluence-cloud/docs/make-your-page-and-its-title-more-memorable/. After it's replaced, API will start returning correct response.
• As an alternative to above, emojis could be replaced or removed via respective PUT or DELETE endpoints from this API group: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-content-properties/. Properties to be removed/replaced have keys emoji-title-draft and emoji-title-published.