feat: [FC-0044] Unit page API as DRF

[ruzniaievdm]

Description

This PR addresses a need in the development of the Course Unit Page feature within the frontend-app-course-authoring repository. The core objective is the implement of a DRF endpoint designed to render and deliver data within the unit.

The existing data structure can be explored in the edx-platform/cms/templates/container.html.

To promote code reusability and avoid duplications, the decision was made to centralize common logic within a utils.py. This approach simplifies code maintenance.

This PR includes additional modifications to various files to prevent errors on the api-docs page and resolving issues related to circular imports.

Testing instructions

1. Run master devstack.
2. Start platform make dev.up.lms+cms and make checkout on this branch.
3. Go to http://localhost:18010/api-docs.
4. Find the required API endpoint /api/contentstore/v1/container_handler/{usage_key_string}.
5. Open needed unit page in cms http://localhost:18010/container/{usage_key_string} and make sure nothing has changed.
6. Copy usage_key_string from previous step and paste it to required API endpoint to get data for unit.

[openedx-webhooks]

Thanks for the pull request, @ruzniaievdm! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[arbrandes]

@ruzniaievdm, can you add a brief description of the motivation behind this PR, and a summary of the potential risks if this is merged? For example, what kind of impact surface area are we talking about? Are these views used everywhere in Studio, or is it a new thing?

It would also be good to have a brief set of instructions on how to test this manually.

[arbrandes]

I've read the code: the logic seems solid. I've also tested this locally on a Tutor nightly dev enviroment running on latest master. Everything seems to work fine.

Can't object in principle, either: more DRF = more good. ;)

[openedx-webhooks]

@ruzniaievdm 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.