feat: add support for Angular 17

[mivaylo]

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?

Issue Number: CDE-1597

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

This is not exactly port (as it was not cherrypicked) but it adds the same change as this PR: #1094

Tested with this PR: #1313

[github-actions]

👋 @mivaylo,

• 🙏 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 Slack channel

Thank you,

🤖 Clarity Release Bot

[kevinbuhmann]

This is a feature, not a chore, because it adds support for v17 in the peer dependency list. Please change the PR title to feat: add support for Angular 17 or similar.

[mivaylo]

This is a feature, not a chore, because it adds support for v17 in the peer dependency list. Please change the PR title to feat: add support for Angular 17 or similar.

@kevinbuhmann , updated, thanks

[github-actions]

Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.