[BB-5329] Added date configuration to Schedule & Details settings page

[farhaanbukhsh]

Description

Adds the ability to configure Schedule & Details settings page with the ability to show dd/mm/yyyy format. Default setting maintains existing behavior and doesn't introduce anything new.
Why:
Some areas of the world operate with the day-first: dd/mm/yyyy rather than mm/dd/yyyy.

JIRA tickets: BB-5329

Discussions: Link to any public dicussions about this PR or the design/architecture. Otherwise omit this.

Dependencies: None

Screenshots:

Sandbox URL: TBD - sandbox is being provisioned.

Merge deadline: None

Testing instructions

• Initialize lilac devstack to use branch
• Look at the studio --> course(Demo Course) --> settings --> Schedule and Details
• Go under the Course Schedule section and you will see the date format is MM/DD/YYYY
• Now drop in the studio shell make dev.shell.studio
• Edit /edx/etc/studio.yml and under Features add SCHEDULE_DETAIL_FORMAT: 'DD/MM/YYYY'

FEATURES: ... SCHEDULE_DETAIL_FORMAT: 'DD/MM/YYYY' ...

• Restart studio make dev.restart-devserver.studio
• Now check the page again you will see the date format has changed to DD/MM/YYYY

Author notes and concerns:

• No change to role(s)
• There is no before or after, as the change includes default configuration to remain consistent with preexisting behavior.
• https://github.com/open-craft/edx-platform/blob/jbcurtin/bb-5429-date-configuration/cms/envs/common.py#L459

Reviewers

• @farhaanbukhsh
• @jbcurtin

[farhaanbukhsh]

👍

• ✅ I tested this, on the devstack with testing instructions
• ✅ 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.

@jbcurtin you need to approve this PR I have opened this to save some time, hope you don't mind it :) and I am really sorry to close the previous PR it was against the wrong branch 🙇🏾

[Cup0fCoffee]

@farhaanbukhsh @jbcurtin We were able to remove the custom changes from the UQ's custom branch and switched to the common branch to reduce maintenance.
I'm closing this PR.