fix: swagger docs ref_name conflicts

[navinkarkera]

Description

Fixes following error while rendering automatic swagger docs:

cms-1  | drf_yasg.errors.SwaggerGenerationError: Schema for <class 'cms.djangoapps.contentstore.rest_api.v0.serializers.authoring_grading.CourseGradingModelSerializer'> would override distinct serializer <class 'cms.djangoapps.contentstore.rest_api.v1.serializers.grading.CourseGradingModelSerializer'> because they implicitly share the same ref_name; explicitly set the ref_name attribute on both serializers' Meta classes

Supporting information

• Private-ref: FAL-4039
• Relates to: fix: errors during swagger api-docs generation openedx-learning#273
• Part-of: Swagger generation on edx-platform CMS broken due to ObjectTag serializer has a "name" field openedx-learning#272

Testing instructions

• Checkout this PR and fix: errors during swagger api-docs generation openedx-learning#273
• Visit the Studio API docs page, e.g http://studio.local.openedx.io:8001/api-docs/
  Note that the page renders now without error.

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

Other information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
• Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
• If your database migration can't be rolled back easily.

[openedx-webhooks]

Thanks for the pull request, @navinkarkera!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[pomegranited]

👍 Thank you for your thorough work here @navinkarkera !

• I tested this by running this PR with the updated requirement from fix: errors during swagger api-docs generation openedx-learning#273 in my tutor dev stack.
  Watched the CMS logs while loading http://local.openedx.io:8001/api-docs/, and noted that all the errors and warnings that this page used to generate are now gone.
  Spot-checked a few of the modified APIs by executing them in the browser.
• I read through the code
• I checked for accessibility issues N/A
• Includes documentation inline where views were excluded from the swagger API docs.
• User-facing strings are extracted for translation N/A

[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 production environment.