feat: add support for pathway retirement

[zawan-ila]

PROD-2973

This PR:-

• Adds the ADR for pathways retirement
• Adds the status field to Pathway objects
• Exposes the status field in the Pathway APIs
• Allows filtering the pathway api by status

[AfaqShuaib09]

ADR wise, LGTM. Not approving it yet since you mentioned you're working on the code changes

[DawoudSheraz]

• Please update/add tests
• Update PR title and description

[justinhynes]

The ADR and changes seem reasonable to me.

Question: Did this change need to be presented as a proposal to Product at Axim or the Product working group for Open edX?

[deborahgu]

this seems sensible to me.

re: @justinhynes's quetion: I'm not sure if Axim would feel anything going into course discovery (except breaking changes) would require going through the product WG, since the plan is to deprecate course-discovery, I believe. (#4449) That being said, I have mixed feelings over whether or not this constitutes a breaking change. Arguably if we coordinate the rollout of all of the different changes (e.g. course-discovery, credentials, etc.) it's all just internals, but the "arguably" is doing a lot of work there. tl;dr I agree that it's worth clearing this through product review.

[DawoudSheraz]

this seems sensible to me.

re: @justinhynes's quetion: I'm not sure if Axim would feel anything going into course discovery (except breaking changes) would require going through the product WG, since the plan is to deprecate course-discovery, I believe. (#4449) That being said, I have mixed feelings over whether or not this constitutes a breaking change. Arguably if we coordinate the rollout of all of the different changes (e.g. course-discovery, credentials, etc.) it's all just internals, but the "arguably" is doing a lot of work there. tl;dr I agree that it's worth clearing this through product review.

I don't think we need anything from Axim on this, especially after the deprecation. I don't think this is a breaking change. If we were only sending the published pathways from API after this change, that would have constituted the breaking change. However, as Ali Nawaz added in ADR, we have added the filter capability in API and then leaving it to consumers to handle it as they see fit.