Implement feedback object hierarchy

[ozer550]

Summary

Create utility functions and classes to support the Feeback project.

Description of the change(s) you made

• Add required classes to implement feedback object hierarchy.
• Add unit tests related to implemented classes.
• Add constants involved with the feedback mechanism.

Manual verification steps performed

• Run frontend tests

Reviewer guidance

How can a reviewer test these changes?

• Run the feedbackUtils.spec.js test file.

References

closes #4366

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[ozer550]

@vkWeb mentioned that, it seems like target_topic_id can be ommited here. We can access the parent_id field of the contentNode to access the target_topic_id.

[bjester]

Nothing blocking. The most important aspect to revisit would be the URL handling, as I mentioned, but that would be easiest once the APIs are actually built.

[bjester]

What was eslint complaining about here?

[ozer550]

Currently the BaseFeedbackEvent is not being used anywhere as the recommendations core classes like ReccommendationInteractionEvent and ReccommendationEvent class are still to be added! Hence its suggesting to remove the unused class.

[bjester]

So this file is treated as an ES module, meaning if variables aren't used in the file then this would occur. Nothing is exported from this module, so doing that could perhaps resolve it?

[bjester]

Great job on writing up some tests!