feat: Commerce Coordinator step in retirement pipeline

[JadeyOlivier]

Adding caller function for new Commerce Coordinator retirement step.

[justinhynes]

I don't feel comfortable giving it a 👍 yet with the tests failing, but I think the approach here is great. I can see us using this to remove some of the other 2U-specific retirement pieces that already exist in the codebase too.

Are there plans to update the Open edX documentation with info on this new feature? I could see it being useful for other folks in the community, or even just future us. There are so many settings and configuration pieces in the monolith that configuration options and discoverability is difficult.

EDIT: Slightly worried I might send you on a wild goose chase with regards to adding new documentation. I noticed today that it seems a lot of retirement documentation exists in the /scripts/user_retirement/docs folder, so this might be the more appropriate place to document this feature?

[justinhynes]

Thanks for your patience through this saga!

[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.

[HassanJaveed84]

@JadeyOlivier @justinhynes

I believe this PR is causing our retirement pipeline to fail on requirements installation.
If it is a matter of bumping up the python version, please let us know.
We would like to fix it as soon as possible.

08:45:30 ERROR: Ignored the following versions that require a different python version: 0.15.0 Requires-Python >=3.9; 0.16.0 Requires-Python >=3.9; 5.0 Requires-Python >=3.10; 5.0.1 Requires-Python >=3.10; 5.0.2 Requires-Python >=3.10; 5.0.3 Requires-Python >=3.10; 5.0.4 Requires-Python >=3.10; 5.0.5 Requires-Python >=3.10; 5.0.6 Requires-Python >=3.10; 5.0.7 Requires-Python >=3.10; 5.0.8 Requires-Python >=3.10; 5.0a1 Requires-Python >=3.10; 5.0b1 Requires-Python >=3.10; 5.0rc1 Requires-Python >=3.10; 5.1 Requires-Python >=3.10; 5.1a1 Requires-Python >=3.10; 5.1b1 Requires-Python >=3.10; 5.1rc1 Requires-Python >=3.10
08:45:30 ERROR: Could not find a version that satisfies the requirement django-mptt==0.16.0 (from versions: 0.1, 0.2, 0.2.1, 0.3.0, 0.3.1, 0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.6.0, 0.6.1, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.13.4, 0.14.0)
08:45:30 ERROR: No matching distribution found for django-mptt==0.16.0
08:45:30 

[justinhynes]

Ah, yeah. I think you're correct about needing to bump the Python version.

The generic retirement feature requires the use of Django settings, and we ended up having to pull in a bunch of edx-platform requirements... which I believe are generated for Python 3.11.

Many apologies here, we should have passed this by data platform first.

Would you like me to prepare a revert? I'm not sure if @JadeyOlivier is still around as I believe they work out of SA, but I'm happy to get one staged.

[HassanJaveed84]

Ah, yeah. I think you're correct about needing to bump the Python version.

The generic retirement feature requires the use of Django settings, and we ended up having to pull in a bunch of edx-platform requirements... which I believe are generated for Python 3.11.

Many apologies here, we should have passed this by data platform first.

Would you like me to prepare a revert? I'm not sure if @JadeyOlivier is still around as I believe they work out of SA, but I'm happy to get one staged.

Switching to 3.11 resulted in different errors.
Can we revert this for now so we can better test it before rolling out ?