Preview requires server to server communication

[jballe]

What happened?

Description

Metadata editing was introduced in #29 which removes the requirement for server to server communication. Really good!
However, when use the preview button in Page Builder, there is still some server communication going on. The workaround currently for the ASP.NET based site is to enable support for ExperienceEditor but it puts more requirements on the infrastructure. As preview is working in Content SDK without Experience Editor support, we should also be able to do that with the ASP.NET Core SDK. I don't know the requirements, should the site indicate something more to pages or is there something in Pages that needs to be changed.

Reproduction Steps

1. Deploy rendering host using .WithSitecorePages(...) but without .WithExperienceEditor(...)
2. Open Page Builder on a page. Choose the preview button (the eye icon) in the top right corner

Actual Behavior

The user ends on an url for the CM of the authoring environment with parameters (?sc_horizon=preview&sc_headless_mode=preview&sc_horizonhost=http://pages.sitecore.cloud.io&sc_itemid=...&sc_lang=..&sc_site=...&sc_version=...

Expected Behavior

Show the actual rendered page

Code of Conduct

• I agree to follow this project's Code of Conduct

[sc-ivanlieckens]

This is being resolved by the Pages Team under PGS-5432.