feat: add a feature flag to disable dates tab for all courses

[Cup0fCoffee]

Description

This PR adds a feature flag that allows disabling dates tab for all courses.

Testing instructions

1. Run the platform in a way that is convenient for you - tutor, devstack, etc.
2. Checkout this PR
3. Check that by default courses have dates tab (you might need to run ./manage.py cms backfill_course_tabs for them to appear, for example if running on devstack)
4. Set the DISABLE_DATES_TAB flag to True.
5. Validate that all courses now have the dates tab hidden, as it is no longer enabled.

Deadline

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

[openedx-webhooks]

Thanks for the pull request, @Cup0fCoffee! 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.

[ArturGaspar]

Instead of an instance-wide setting, I think it makes more sense to make this configurable per course, by setting is_hideable = True in the DatesTab class, and creating a course app to configure it in case the pages and resources MFE is enabled (e.g.

edx-platform/lms/djangoapps/courseware/plugins.py

Line 48 in a10fce3

def set_enabled(cls, course_key: CourseKey, enabled: bool, user: 'User') -> bool:

).

[ArturGaspar]

👍

• I tested this: setting the feature flag hides the dates tab when it is otherwise shown
• I read through the code
• I checked for accessibility issues
• Includes documentation
• I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository. - N/A

[farhaanbukhsh]

@mphilbrick211 does this require a product review as well?

[farhaanbukhsh]

@itsjeyd same question as above?

[itsjeyd]

@farhaanbukhsh Please have a look at Does my contribution require Product Review?, it should help you with answering your question :)

[farhaanbukhsh]

@mphilbrick211 @itsjeyd it does qualify for product review. :)

[itsjeyd]

@farhaanbukhsh Alright, thanks for checking. The next step will be for you to complete the first two items listed here to get the product review process going.

CC @mphilbrick211