Issue Summary

After a recent backend change, the validation of legacy pages to understand whether the content is or is not supported to be converted to the new editing experience is being passed, popping up the message stating the page isn't every time we edit the pages.

Steps to Reproduce

1. Create a page using the Legacy Editor template;
2. Insert some simple text on the page and publish it;
3. Edit this page.

Expected Results

The bottom bar informing that the page is supported to be converted to the new editor is shown up as usual.

Actual Results

In addition to the bottom bar, an in-editor message pops up stating that the page is not supported to be converted - even though it does.
"This page uses the old editor

Some of its content isn't yet supported in the updated editor."

Notes:

• It is known that a recent change in the backend modified the validation of the old pages, so the parameter isUnsupportedContent is no longer being passed, resulting in that in-editor message popping up every time

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available