Explicitely exclude files from being linted by MegaLinter

[johannaengland]

Scope and purpose

MegaLinter passes a list of files to black and ruff without using force-exclude the linters did ignore the basic exclude configuration in that case, which is why FILTER_REGEX_EXCLUDE was needed.

The issue I made in MegaLinter about that topic: https://github.com/oxsecurity/megalinter/issues/3915 Force-exclude in black configuration: https://black.readthedocs.io/en/stable/usage_and_configuration/the_basics.html#force-exclude Force-exclude in ruff configuration: https://docs.astral.sh/ruff/settings/#force-exclude

Contributor Checklist

Every pull request should have this checklist filled out, no matter how small it is. More information about contributing to Zino can be found in the README.

• [ ] Added a changelog fragment for towncrier
• [ ] Added/amended tests for new/changed code
• [X] Added/changed documentation
• [X] Linted/formatted the code with black, ruff and isort, easiest by using pre-commit
• [X] The first line of the commit message continues the sentence "If applied, this commit will ...", starts with a capital letter, does not end with punctuation and is 50 characters or less long. See https://cbea.ms/git-commit/
• [ ] If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.57%. Comparing base (c0c5696) to head (92a0c65). Report is 5 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #358 +/- ## ======================================= Coverage 98.57% 98.57% ======================================= Files 77 77 Lines 9699 9699 ======================================= Hits 9560 9560 Misses 139 139 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.