feat: replace signal handler with event producer config

[navinkarkera]

Description: Replace the hard-coded signal handler with event bus producer config. See openedx/openedx-events#249 and openedx/edx-platform#32874 for more details.

JIRA: Private-ref: BB-7666

Dependencies:

• feat: enable producing to event bus via settings openedx-events#249
• feat: use event producer config edx-platform#32874

Merge deadline: List merge deadline (if any)

Testing instructions:

• Setup master devstack
• Run make lms-up to get lms up and running.
• Create lms shell using make lms-shell.
• Install this plugin by running pip install -e /edx/src/xblock-skill-tagging/ (assuming this repo is cloned in <devstack-base-dir>/src/)
• Include EVENT_BUS_PRODUCER_CONFIG setting as per the configuration in README in lms/envs/private.py to push XBLOCK_SKILL_VERIFIED to event bus.
• Run below snippet to send XBLOCK_SKILL_VERIFIED event.

from datetime import datetime, timezone
from openedx_events.learning.signals import XBLOCK_SKILL_VERIFIED
from openedx_events.learning.data import XBlockSkillVerificationData
XBLOCK_SKILL_VERIFIED.send_event(
    time=datetime.now(timezone.utc),
    xblock_info=XBlockSkillVerificationData(
        usage_key="block-v1:edx+DemoX+Demo_course+type@video+block@UaEBjyMjcLW65gaTXggB93WmvoxGAJa0JeHRrDThk",
        verified_skills=[1, 2],
        ignored_skills=[3, 4],
    )
)

• It should print something like below:

2023-08-29 12:03:46,477 INFO 1502 [edx_event_bus_redis.internal.producer] [user None] [ip None] producer.py:82 - Message delivered to Redis event bus: topic=dev-learning-custom-xblock-skill-verfied, message_id=1b5934e4-4664-11ee-83e5-0242ac12000b, signal=<
OpenEdxPublicSignal: org.openedx.learning.xblock.skill.verified.v1>, redis_msg_id=b'1693310626477-0'
[(<function general_signal_handler at 0x7fcf6e0e2a60>, None)]

• You can play with the topic name and other setting to see the changes.

Reviewers:

• @sameenfatima78

Merge checklist:

• All reviewers approved
• CI build is green
• Version bumped
• Changelog record added
• Documentation updated (not only docstrings)
• Commits are squashed

Post merge:

• Create a tag
• Check new version is pushed to PyPI after tag-triggered build is
  finished.
• Delete working branch (if not needed anymore)

Author concerns: List any concerns about this PR - inelegant
solutions, hacks, quick-and-dirty implementations, concerns about
migrations, etc.

[tecoholic]

@navinkarkera 👍

• I tested this: Followed the testing instructions in platform PR and verified, signals are produced from the config without custom handlers.
• I read through the code
• I checked for accessibility issues
• Includes documentation

[openedx-webhooks]

Thanks for the pull request, @navinkarkera! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[mphilbrick211]

Hi @navinkarkera! Would you mind resolving the branch conflicts that have popped up? Then I can get it reviewed. Thanks!

[mphilbrick211]

Hi @sameenfatima78! Just following up on this :)

[navinkarkera]

@sameenfatima78 Once openedx/openedx-events#272 is merged, I'll update this PR based on the decision in the ADR.

[mphilbrick211]

@navinkarkera now that #272 is merged, is this now ready-to-go?

[navinkarkera]

@mphilbrick211 @sameenfatima78 Thanks for your patience. This is now ready to be merged.

Please wait, I'll also update the requirements.

Done. Now it is ready.

[mphilbrick211]

@navinkarkera - looks like there's still a failing test. Would you mind taking a look?

[navinkarkera]

@mphilbrick211 @sameenfatima78 Sorry for the delay. Fixed the failing test and manually tested verification event in devstack.

[navinkarkera]

@sameenfatima78 Gentle reminder.

[sameenfatima78]

Tagging @irfanuddinahmad here for review.