i18n: Preserve block attribute encoding

[MaggieCabrera]

Summary

Preserve WordPress Core’s encoding for block attributes during localized export.

Only localized values are substituted after serialization, leaving all other attributes encoded consistently with Core.

Test plan

• vendor/bin/phpunit -c phpunit.xml.dist --verbose --filter CBT_Theme_Locale_EscapeBlockAttributes
• vendor/bin/phpunit -c phpunit.xml.dist --verbose --group locale
• vendor/bin/phpcs --standard=phpcs.xml.dist includes/create-theme/theme-locale.php tests/CbtThemeLocale/escapeBlockAttributes.php
• Confirmed localized labels still work and encoded sibling attributes remain unchanged in generated pattern PHP.

[Copilot]

Pull request overview

This PR adjusts localized export handling so block attribute JSON retains WordPress Core’s canonical encoding for non-localized attributes, while still substituting localized attribute values after serialization.

Changes:

• Update CBT_Theme_Locale::escape_block_attribute_strings() to re-serialize attributes via serialize_block_attributes() and then replace localized values using unique placeholders.
• Add a unit test ensuring sibling (non-localized) attributes keep Core’s encoding (e.g., \u003c, \u0022, \u002d\u002d) while localized values are still injected.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
includes/create-theme/theme-locale.php	Reworks attribute re-encoding to preserve Core encoding and only substitute localized values post-serialization.
tests/CbtThemeLocale/escapeBlockAttributes.php	Adds regression coverage to confirm non-localized attributes remain Core-encoded after localization processing.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.