fix(a11y): stack-view - no proper heading hierarchy maintained in the page

[andyfeds]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

No proper heading hierarchy maintained in the page in case of a stack-block component, as the role is fixed as "heading".
If a user wants to change or omit the role, they can't, because our current implementation forces the heading role and level.
Issue Number: CDE-1634

What is the new behavior?

The below changes are made as mentioned in the JIRA ticket:

• If no role is provided, we add role="heading" by default and add the aria-level based on common component usage.
• The user can change the role or the aria level (if the role is not "heading", we omit the aria-level attribute).
• If the user decides they don't want the "role" attribute at all, they can pass in an undefined value "undefined" and we won't add the role or aria-level attribute.

A new input clrSbAriaRole is added to the stack-block, so the user can pass/configure the aria role.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[github-actions]

👋 @andyfeds,

• 🙏 The Clarity team thanks you for opening a pull request
• 🎉 The build for this PR has succeeded
• 🔍 The PR is now ready for review
• 🍿 In the meantime, view a preview of this PR
• 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal Clarity Support space

Thank you,

🤖 Clarity Release Bot

[sandeepkulki]

Changes are approved

[github-actions]

This PR introduces visual changes: 952f331
If these changes are intended and correct, please cherry-pick the above commit to this PR.

git checkout a11y/CDE-1634
git fetch https://github.com/vmware-clarity/ng-clarity.git 952f33137551130cafe770c1545d01fd49cfd83d
git cherry-pick 952f33137551130cafe770c1545d01fd49cfd83d
git push

[github-actions]

This PR introduces visual changes: c636c9d
If these changes are intended and correct, please cherry-pick the above commit to this PR.

git checkout a11y/CDE-1634
git fetch https://github.com/vmware-clarity/ng-clarity.git c636c9d899dea12a6d7ca63f7666c9a00238b805
git cherry-pick c636c9d899dea12a6d7ca63f7666c9a00238b805
git push

[github-actions]

This PR introduces visual changes: 079ec02
If these changes are intended and correct, please cherry-pick the above commit to this PR.

git checkout a11y/CDE-1634
git fetch https://github.com/vmware-clarity/ng-clarity.git 079ec0295681f37805a4eb48b7e4f3c7d2fa378c
git cherry-pick 079ec0295681f37805a4eb48b7e4f3c7d2fa378c
git push

[github-actions]

This PR introduces visual changes: 08f14d1
If these changes are intended and correct, please cherry-pick the above commit to this PR.

git checkout a11y/CDE-1634
git fetch https://github.com/vmware-clarity/ng-clarity.git 08f14d1c83b3a20f6d076cb29038cffbfb0ca489
git cherry-pick 08f14d1c83b3a20f6d076cb29038cffbfb0ca489
git push

[github-actions]

This PR introduces visual changes: 020c3ee
If these changes are intended and correct, please cherry-pick the above commit to this PR.

git checkout a11y/CDE-1634
git fetch https://github.com/vmware-clarity/ng-clarity.git 020c3eee14cce6c3c448369951366b402dd9dc16
git cherry-pick 020c3eee14cce6c3c448369951366b402dd9dc16
git push

[andyfeds]

Contains breaking changes, will be part of v18 release.