feat: adds hub.related.contentItems.getByDeliveryKey() to lookup a co…

[easen-amp]

…ntent-item by its delivery key

Pull request checklist

Please check if your PR fulfills the following requirements:

• Build (npm run build) was run locally and any changes were pushed
• Tests (npm run test) for the changes have been added (for bug fixes / features)
• Docs (npm run doc) have been reviewed and added / updated if needed (for bug fixes / features)
• PR title and git commit messages conform to the conventionalcommits specification

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behaviour?

What is the new behaviour?

• able to fetch a content item by it's delivery key

Does this introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 10202089589

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.004%) to 95.336%

---

Totals
Change from base Build 7813868124:	0.004%
Covered Lines:	977
Relevant Lines:	996

---

💛 - Coveralls

[amplience-snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[amplience-snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.