feat: Move Program Certificate event publishing to the monolith

[rahulkanneri-2u]

Description

This PR moves program certificate event publishing from the Credentials IDA to the LMS monolith.

When a program certificate is awarded or revoked, the LMS now publishes the following events to the event bus:

• PROGRAM_CERTIFICATE_AWARDED
• PROGRAM_CERTIFICATE_REVOKED

These events are disabled by default until the Credentials IDA is ready to consume them instead of relying on direct REST API calls.

Supporting Information

This is related to the initiative to move program certificate lifecycle event publishing into edx-platform using [openedx-events](https://github.com/openedx/openedx-events).

Testing Instructions

1. Run the programs task tests:

   pytest openedx/core/djangoapps/programs/tests/ -v

2. To test event emission manually, enable the feature flags in your settings:

   EVENT_BUS_PRODUCER_CONFIG[
       "org.openedx.learning.program.certificate.awarded.v1"
   ]["learning-program-certificate-lifecycle"]["enabled"] = True
   
   EVENT_BUS_PRODUCER_CONFIG[
       "org.openedx.learning.program.certificate.revoked.v1"
   ]["learning-program-certificate-lifecycle"]["enabled"] = True

3. Trigger a program certificate award or revocation.

4. Verify that the corresponding event is published to the event bus.

Deadline

None

Other Information

• No database migrations are required.
• Both new event bus entries are disabled by default with enabled: False until the Credentials IDA is ready to consume them.
• The events carry a ProgramCertificateData payload with user information and the program UUID.
• The title, program_type, and uuid fields on the program/certificate are intentionally left as empty strings because the LMS does not have authoritative access to that data at award time.

[openedx-webhooks]

Thanks for the pull request, @rahulkanneri-2u!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[mphilbrick211]

Hi @rahulkanneri-2u! It looks like you're contributing on behalf of 2U. In order for your CLA check to turn green (and if you have not done so already), please have your manager reach out to oscm@axim.org to have you added to our existing entity agreement.