feat(fragment) - inherit section dataset

[andreituicu]

Building on @rofe's #4 where the fragment section's classes were propagated to the target section, this PR also propagates the dataset.
In the boilerplate, section metadata:

• styles are added as classes on the fragment section https://github.com/adobe/aem-boilerplate/blob/main/scripts/aem.js#L451-L453 are added as classes and propagated (already done by feat(fragment): inherit section classes #4)
• all other keys/values are added in the section's data set https://github.com/adobe/aem-boilerplate/blob/main/scripts/aem.js#L455, and should be propagated (addressed by this PR)

Test URLs:
Before: https://main--helix-block-collection--adobe.hlx.page/block-collection/fragment
After: (cannot add after url, as I don't have permissions to push a branch in this repo)

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some test suites that validate the page speed.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-run PSI Checks

[rofe]

@andreituicu

cannot add after url, as I don't have permissions to push a branch in this repo

Alternatively, you can provide a URL on your fork.

[andreituicu]

@rofe I can't seem to make the fork work on the fragment-data branch... after installing the aem-code-sync application. I can access https://main--helix-block-collection--andreituicu.hlx.live/block-collection/fragment , but https://fragment-data--helix-block-collection--andreituicu.hlx.live/block-collection/fragment still returns 404.

I can show this in action in the project I'm currently working on:

• https://main--servicenow--hlxsites.hlx.live/blogs/topics/ai-and-automation

The sidebar from that page is a (auto-blocked) fragment.
In the fragment: https://main--servicenow--hlxsites.hlx.live/blogs/fragments/sidebar-common-fragment
We have the following section metadata

Before:

• The style class (sidebar) was being propagated to the destination section, because of your changes from feat(fragment): inherit section classes #4 ✅
• The data-start-sidebar-at-section="1" was not being propagated to the destination section ❌

After:
https://main--servicenow--hlxsites.hlx.live/blogs/topics/ai-and-automation

• The data-start-sidebar-at-section="1" is also propagated to the destination section ✅

Is this helpful?

[rofe]

https://fragment-data--helix-block-collection--andreituicu.hlx.live/block-collection/fragment still returns 404.
Yes, this is a known issue: if you created the branch before adding the bot, it will not automatically be sync'ed. You can sync it by POSTing to /*: https://www.aem.live/docs/admin.html#tag/code/operation/updateCode

[aem-code-sync]

Page	Scores	Audits	Google
/block-collection/fragment
/block-collection/fragment