Standardize ContentCardList Component and Introduce ViewMoreButtonStates

[GarvitSinghal47]

Fixes #11771

Summary

In the process of content creation, we drew inspiration from previous Lesson resource selection components, specifically the ContentCardList component. However, considering the component's last update was three years ago, there are noticeable inconsistencies that we aim to address for a more unified developer interface.

The viewMoreButtonState prop in the ContentCardList component currently relies on a string input. To enhance consistency and maintainability, we propose the transition to a constant-based approach.

Acceptance Criteria:
View More Button State

• Created and exported a new object named ViewMoreButtonStates in the coach/.../constants/index.js file, structured similarly to existing constants.
• The new object manages the following states:
  • Loading (previously denoted as waiting)
  • Has more (previously determined by not passing specific strings for loading or not having more)
  • No more
  • Error
• ContentCardList has been updated to validate the viewMoreButtonStates prop against these constants, ensuring only valid constants are accepted.
• ContentCardList no longer relies on the absence of errors to display the button; instead, it checks for the ViewMoreButtonStates.hasMore state.
• Components using the ContentCardList have been updated to incorporate the new constants when passing the prop. Specifically, adjustments have been made in LessonResourceSelectionPage/index.vue, CreateExamPage/index.vue, and CreateExamPage/CreatePracticeQuiz.vue.

These changes aim to standardize the ContentCardList component and introduce a clear set of constants for the viewMoreButtonState prop. This not only improves code consistency but also facilitates easier maintenance and future development.

…

References

…

Reviewer guidance

…

---

Testing checklist

• 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
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• 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

[nucleogenesis]

I couldn't manage to replicate getting "View more" in the lesson creation context but the code changes there LGTM.

Things worked properly in the quiz context in any case!

Thanks so much @GarvitSinghal47

[nucleogenesis]

Force merging this as I've tested it locally but cannot restart the stalled check