feat: Add override option to upgrade CTA utils and add course_run_key identifier

[aht007]

Description

This PR introduces override capabilities to the EcommerceService class utilities. Currently, upgrade CTA URLs across edx-platform depend on the get_checkout_page_url and get_absolute_ecommerce_url methods, both of which are closely tied to the Oscar-based ecommerce system. This tight coupling presents challenges when attempting to integrate alternative ecommerce systems. With this PR, alternative implementations for these methods can be provided by leveraging the pluggable_override functionality from edx_django_utils.

Other information

• Does this change depend on other changes elsewhere?
  To utilize this functionality, developers must define the path to the alternative implementations in the settings file using the override flags.
  Override flags being introduced in this PR:

1. OVERRIDE_GET_CHECKOUT_PAGE_URL
2. OVERRIDE_GET_ABSOLUTE_ECOMMERCE_URL

Override implementation needs to be housed somewhere else outside of edx-platform which can be a pluggable app installed independently in edx-platform requirements

[NawfalAhmed]

Nice work!

[bmtcril]

Hi @aht007 , I was working with @grmartin on this deprecation ticket: openedx/public-engineering#272 . This PR seems like an incremental step toward the goals in that ticket, which is great!

As mentioned in the ticket, the whole commerce app has been slated for deprecation for around 5 years. The goal is to find the places that explicitly call into commerce and make them more generic hooks / events/ filters so that any system (even non-commerce, such as a course recommendation engine) can extend them with more flexibility without breaking 2U's current design.

The hope was that we could add in those extension points as part of the deprecation to prevent you all from having to do all of this work now, then have to redo everything again when we deprecate commerce. By doing that work yourselves you would be best able to make sure the 2U specific functionality is preserved and tested as part of development, rather than needing to work with a contribution from the community that may not fit your needs.

To be clear, I don't have any problems with this PR as-is but want to make sure the direction is clear and hopefully save you all some work going forward.

[aht007]

Hi @brian-smith-tcril,

Thank you for sharing your thoughts and reviewing the PR.
At the moment, our priorities and timelines don't allow us to take on this work, as it's a significant change that requires thorough coordination and communication, in addition to the technical aspects. That said, I’ll consult with the team and managers and follow up with you on this.

However, since the discussions around this could take some time, I would appreciate it if we could proceed with this PR for now.

[bmtcril]

@aht007 I think you pinged the wrong Brian, but yes I think you can consider that feedback non-blocking. It looks like you already have the required approvals so you should be all set.

[aht007]

@bmtcril Ah sorry for the oversight and thank you.

[edx-pipeline-bot]

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

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.