Enable Extracted Discussion XBlock

[salman2013]

Description:

This PR enables the extracted discussion xblock in edx-platform

Setting:

USE_EXTRACTED_DISCUSSION_BLOCK = True

Ticket: openedx/public-engineering#501

Testing Details:

1. Discussion Block — Studio & LMS

#	Scenario	Expected Result
1	Add a Discussion block from the Studio unit page components	Block is added successfully
2	Navigate to the corresponding LMS course unit page	Discussion block is visible
3	Use the show/hide button on the discussion block	Block toggles between visible and hidden states

---

2. Discussion Post

#	Scenario	Expected Result
1	Click the Add Post button	Post creation form opens
2	Select post type: Question or Discussion	Correct post type is selected
3	Fill in Title, Description, and Content fields	Fields accept and display input correctly
4	Click Follow on a post	Post is followed; button changes to Unfollow
5	Click Unfollow on a followed post	Post is unfollowed; button changes back to Follow

---

3. Discussion Post — Responses

#	Scenario	Expected Result
1	Click Add Response on a post	Response is added successfully
2	Click Edit on an existing response	Response content becomes editable and can be saved
3	Click Delete on an existing response	Response is removed
4	Click Mark as Answer on a response	Response is marked as the accepted answer
5	Click Comment on a response	Comment is added under the response

[openedx-webhooks]

Thanks for the pull request, @salman2013!

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.

[salman2013]

The extracted discussion xblock has been tested with all the scenarios which are mentioned on ticket.
openedx/public-engineering#501