[FC-0018] feat: Standardize XblockView/XblockCreateView

[taimoor-ahmed-1]

Description:

The FC-0118 initiative introduces a comprehensive standardization of APIs across the platform, guided by 15 newly defined Architectural Decision Records (ADRs). These ADRs collectively establish consistent patterns for serializers, permissions, error handling, pagination, filtering, authentication, versioning, and overall API design. Through this effort, existing endpoints are being refactored and aligned to ensure uniformity, improved developer experience, and long-term maintainability, while also reducing redundancy and inconsistencies across services.

Checklist:

• 0025 – Standardize Serializer Usage
• 0026 – Standardize Permission Classes
• 0027 – Standardize API Documentation & Schema Coverage
• 0028 – Standardize RESTful API Endpoints using DRF ViewSets
• 0029 – Standardize Error Responses
• 0030 – Ensure GET Requests are Idempotent
• 0031 – Merge Similar Endpoints
• 0032 – Standardize Pagination Usage
• 0033 – Standardize Filter & Sort using django-filter
• 0034 – Unify Auth (OAuth2 v2)
• 0035 – Port Legacy Django Views to DRF
• 0036 – Normalize Deeply Nested JSON APIs
• 0037 – API Versioning Strategy
• 0038 - Introduce Row level Security Layer
• 0039 – Modulestore CRUD APIs with Custom Serializers
• 0040 – Document & Consolidate Internal APIs used by MFEs

[openedx-webhooks]

Thanks for the pull request, @taimoor-ahmed-1!

This repository is currently maintained by @openedx/wg-maintenance-openedx-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.

Details

---

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.