feat: [FC-0074] add linter for Open edX Filters classes definitions

[mariajgrimaldi]

Description:

This PR adds a custom linter for Open edX Filter classes docstrings to check whether new filters follow the specified format:

        Description:
        Filter used to modify the certificate rendering process.
        ... (more description)
        Filter Type:
            org.openedx.learning.certificate.render.started.v1
        Trigger:
            - Repository: openedx/edx-platform
            - Path: lms/djangoapps/certificates/views/webview.py
            - Function or Method: render_html_view

If a class is missing at least one of the section, then a pylint error is raised:

You can see the linter integrated into the repo in this PR: openedx/openedx-filters#249

I'm open to moving this directly into the openedx-filters repo if needed, considering that the linter is kind of specific to that repository.

Merge checklist:

• All reviewers approved
• CI build is green
• If adding new checks, followed how_tos/0001-adding-new-checks.rst
• Changelog record added (if needed)
• Documentation updated (not only docstrings) (if needed)
• Commits are squashed

[openedx-webhooks]

Thanks for the pull request, @mariajgrimaldi!

This repository is currently maintained by @openedx/axim-engineering.

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

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

---

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.

[sarina]

I'm open to moving this directly into the openedx-filters repo if needed, considering that the linter is kind of specific to that repository.

I pinged the Axim eng team in slack to see if anyone has an opinion on this - I don't, but I'm not a primary maintainer of this repo.

[mariajgrimaldi]

Thank you, @sarina!

I'll tag @openedx/axim-engineering here as the owners according to the catalog-info.yaml.