[Owls] PB-422: Extensions utilizing Page Builder as their content creation tool will break with upgrade

[omiroshnichenko]

Description

We resolved a bug as part of our BiC epic PB-55 which will only be migrated for entities that are declared in our configuration. This means any extension which uses Page Builder as a content creation tool will not be upgraded and thus break. This could use the content to become corrupted if modified by the user without it being migrated. So we reverted bugfix that contains BiC changes

Related Issue

PB-422 Extensions utilizing Page Builder as their content creation tool will break with upgrade

Acceptance

Bugfix should be reverted

Verification Steps

1. Create Page Builder content with one contained row containing a button.
2. Duplicate that row and change the appearance from contained to Full Width.
3. Verify the buttons in each row are not aligned

Screenshots / Screen Captures (if appropriate)

Checklist

• I have updated the documentation accordingly, if necessary.
• I have added tests to cover my changes, if necessary.

[PWAStudioBot]

	Messages
📖	Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.
📖	DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next nightly build run (assuming they are fixed).
📖	Associated JIRA tickets: PB-55.

Generated by 🚫 dangerJS against 651dec8