feat: Language auto tagging library blocks

[yusuf-musleh]

Description

This PR adds functionality of automatically tagging library blocks with a language tag when they created/update and automatically deletes them when they are deleted.

Supporting information

Related Tickets:

• Closes [Tagging] Automatically add system tags for Language (to library blocks) modular-learning#97

Testing instructions

1. Run your devstack on this PR
2. Set the content_tagging.auto waffle flag
3. Make sure you have the library authoring mfe setup and running locally, so you can create library and add blocks to them
4. Navigate to studio then click on the Libraries tab, the library mfe should open
5. From there create a new library if you don't already have, and click on it
6. Before creating new blocks, check the existing object tags in the cms shell (make cms-shell):

>>> from openedx_tagging.core.tagging.models import ObjectTag
>>> ObjectTag.objects.all().count()

1. Back in the library authoring mfe, create a new block, then go back to the shell and check that a new ObjectTag was created, the count should increase and you can also inspect the .last() to see the newly created one
2. Navigate back to the library authoring mfe, and delete the newly created block and confirm in the cms shell that the count when down and the .last() is now longer what it was in the previous step.

---

Private-ref: FAL-3497

[openedx-webhooks]

Thanks for the pull request, @yusuf-musleh! 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.

[rpenido]

Good job @yusuf-musleh! 👍

• I tested this using the Testing Instructions and the tag was correctly applied and removed from the library
• I read through the code
• I checked for accessibility issues
• Includes documentation
• I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository.

I just added a nit about the flag check order.

[bradenmacdonald]

(I know that both of my comments ^ are about existing patterns that you just copied, but I'm wondering why it's like that, so I'd like to consider a simpler version rather than just copying it as-is).

[bradenmacdonald]

Nice, thanks! I'll merge tomorrow

[openedx-webhooks]

@yusuf-musleh 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

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