fix: update release-ulmo branch triggers for pylint and dunder init workflows

[Akanshu-2u]

Description:

Updates GitHub Actions workflow triggers so the release-ulmo branch is included for pylint and dunder-__init__.py verification runs, aligning these checks with the release branch workflow.

Changes:

• Added a push trigger for the dunder __init__.py verification workflow on release-ulmo.
• Updated the pylint workflow push branch filter from master to release-ulmo.

[Copilot]

Pull request overview

Updates GitHub Actions workflow triggers so the release-ulmo branch is included for pylint and dunder-__init__.py verification runs, aligning these checks with the release branch workflow.

Changes:

• Added a push trigger for the dunder __init__.py verification workflow on release-ulmo.
• Updated the pylint workflow push branch filter from master to release-ulmo.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/verify-dunder-init.yml	Adds push trigger on release-ulmo so the workflow runs on direct updates to the release branch.
.github/workflows/pylint-checks.yml	Changes push trigger branch filter to release-ulmo so pylint runs on release branch pushes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[robrap]

Thanks. It's probably fine to merge as-is, but I would (and did) wonder whether this was fixed in openedx for verify-dunder-init.yml? Did you also review? See my related comment.

[robrap]

Unsure if it might make sense to cherry-pick the following commits first, to minimize conflicts during ulmo.1 merge:

• openedx@272b166
• openedx@6c7a95c