feat(microsite): Add Solution Header and Solution Footer blocks used within custom campaign/microsites

[proeung]

Issue

Fixes https://merative.atlassian.net/browse/MERATIVE-878 & https://merative.atlassian.net/browse/MERATIVE-879

Description

New

• Solution Header /blocks/solution-header - This block manages and displays the anchor/table of contents navigation used on a single campaign/microsite.
• Solution Footer /blocks/solution-footer - This block manages and displays fragment/related content (See - website > fragments > footer > footer-small) (see link) for the custom footer.

Changed

• Fixes grid container of the CTA block

Design Specs

• Figma Link - https://www.figma.com/file/vw24IPXXt4vCh9BNumka9A/Web--Merative-Digital-Design-System-2.0?type=design&node-id=496%3A6561&mode=dev

Test URLs

• Before (Changes from main): https://main--merative2--hlxsites.hlx.page/drafts/putra/campaigns/missouri
• After (Changes from this PR): https://feat-solution-header--merative2--proeung.hlx.page/drafts/putra/campaigns/missouri

Testing Instruction

• Visit the "After" deploy preview and ensure that the behaviors and styles of the Header/Nav and Footer align with the design specs.

[aem-code-sync[bot]]

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

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri
/support

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri
/support
/

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri
/support
/

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri
/support
/

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri

[proeung]

@sachinmesh I just pushed up a commit to address some of the spacing and logo size issues that you mentioned above.

As for the height of the borderline on the sticky nav scroll and the gradient on the scroll, let's discuss that on our next design call. I have some concerns about the feasibility given the current timeline and dev resources.

cc: @aavilamer

https://javascript.plainenglish.io/how-to-create-horizontal-vertical-scroll-shadows-26aa7a7f00a0

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/drafts/putra/campaigns/missouri

[proeung]

@keith-kaplan Great! Just need @sachinmesh to re-review/approve and this PR is ready for merge unless there are additional changes.