Pass amp_is_bento_enabled() to AMP_Tag_And_Attribute_Sanitizer as prefer_bento arg

[westonruter]

Given a post that has a Custom HTML block with this content:

<script src="https://cdn.ampproject.org/v0/amp-facebook-page-0.1.mjs" async="" custom-element="amp-facebook-page" type="module" crossorigin="anonymous"></script>

Accessing an AMP page (without Bento enabled) will result in v0.1 of the AMP component added to the page (as expected):

<script src="https://cdn.ampproject.org/v0/amp-facebook-page-0.1.mjs" async="" custom-element="amp-facebook" type="module"></script>

When adding this feature flag plugin to enable bento when ?bento is added to the URL:

if ( isset( $_GET['bento'] ) ) {
	add_filter( 'amp_bento_enabled', '__return_true' );
}

Accessing the same AMP page with Bento still results in the same script being added as opposed to amp-facebook v1.0:

<script src="https://cdn.ampproject.org/v0/amp-facebook-page-0.1.js" async="" custom-element="amp-facebook-page"></script>

With this PR, this is fixed by passing the Bento enabled state to the AMP_Tag_And_Attribute_Sanitizer as the prefer_bento arg. So the resulting page then has:

<script src="https://cdn.ampproject.org/v0/amp-facebook-1.0.js" async="" custom-element="amp-facebook"></script>

(Note that amp-facebook-1.0.js is served rather than amp-facebook-1.0.mjs because SSR for Bento is currently broken per ampproject/amphtml#35485, and so SSR is currently disabled when Bento is enabled.)

Props @pierlon for recognizing this oversight in #6353 (comment).

[github-actions]

Plugin builds for b0a4aca are ready 🛎️!

• Download development build
• Download production build

[dhaval-parekh]

QA Passed

✅ Bento versions of scripts are used instead of the AMP version of the script while enabling bento.