Self paced relative dates

[cpennington]

Please consider the following when opening a pull request:

• Link to the relevant JIRA ticket(s) and tag any relevant team(s).
• Squash your changes down into one or more discrete commits.
  In each commit, include description that could help a developer
  several months from now.
• If running make upgrade, run as close to the time of merging as possible
  to avoid accidentally downgrading someone else's package.
  Put the output of make upgrade in its own separate commit,
  decoupled from other code changes.
• Aim for comprehensive test coverage, but remember that
  automated testing isn't a substitute for manual verification.
• Carefully consider naming, code organization, dependencies when adding new code.
  Code that is amenable to refactoring and improvement benefits all platform developers,
  especially given the size and scope of edx-platform.
  Consult existing Architectural Decision Records (ADRs),
  including those concerning the app(s) you are changing and
  those concerning edx-platform as a whole.

[cpennington]

jenkins run python

[cpennington]

jenkins run quality

[cpennington]

jenkins run a11y

[jlajoie]

Looks good, just minor string questions but shouldn't hold this up from merging.

[Dillon-Dumesnil]

Just one question, but otherwise looks good to me

[cpennington]

jenkins run js

[edx-status-bot]

Your PR has finished running tests. There were no failures.

[edx-pipeline-bot]

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

[edx-pipeline-bot]

EdX Release Notice: This PR may have caused e2e tests to fail on Stage. If you're a member of the edX org, please visit #e2e-troubleshooting on Slack to help diagnose the cause of these failures. Otherwise, it is the reviewer's responsibility. E2E tests have failed. https://gocd.tools.edx.org/go/tab/pipeline/history/deploy_to_stage

[edx-pipeline-bot]

EdX Release Notice: This PR has been deployed to the production environment.