Replace fkirc/skip-duplicate-actions in CI workflows

[rtibbles]

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Replace fkirc/skip-duplicate-actions in morango's four workflows following the Strategy in learningequality/.github#83.

Complexity: Low
Target branch: release-v0.9.x

The Change

• check-docs.yml: no required check. Move its path list to native paths: and delete pre_job.
• check_migrations_sqlite.yml, pre-commit.yml, tox.yml: swap fkirc for dorny/paths-filter in pre_job. Gated jobs keep their job-level if, and tox.yml keeps its required_checks aggregator.
• check_migrations_sqlite.yml: drop the step-level should_skip checks inside migration_test, which its job-level if already covers.

Acceptance Criteria

• No workflow references fkirc/skip-duplicate-actions.
• Every path list keeps its current patterns.
• Required check names are unchanged, and the PR body states that no ruleset change is needed.
• The PR links one run where the gated jobs ran and one where they were skipped with every required check green (a run on the contributor's fork is acceptable).
• actionlint passes on every changed workflow.

AI usage

I used Claude Code to survey this repo's workflows and required checks, and to draft this issue. I chose the approach and reviewed it before filing.

[rtibblesbot]

Plan: Remove fkirc/skip-duplicate-actions from morango's four workflows, keeping every path list and required check name.

• check-docs.yml → native paths:
• check_migrations_sqlite.yml → dorny migrations
• tox.yml → dorny python
• pre-commit.yml → dorny lint with negations
• Self-review the produced code

Assumptions — the issue did not settle these; say so if one is wrong.

• No base: input, per KDS#1338; if wrong, pushes to non-default branches over-run gated jobs until base: is added per kolibri-data-portal#1171.
• "Keeps its current patterns" means the same match set; if the literal '!**.po' is required, PRs touching only nested .po/.json files start running lint.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

• Implemented code following the pre-approved plan using test-driven development (red-green-refactor)
• Ran the project's full test suite and linter before committing
• For UI changes: captured live screenshots to verify rendering
• For backend changes: verified with example API/CLI output