Configure Coverage using new exclude_also option

[deepyaman]

Description

The exclude_also option is newer, and Coverage is trying to lean on it more heavily. The benefit is, you don't need to write the default excludes again (e.g. # pragma: no cover, and whatever may come in the future).

Development notes

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[astrojuanlu]

This looks like a worthy change but I don't fully understand what it implies, leaving this to somebody else from engineering to comment 🙏🏼

[deepyaman]

The exclude_also option is newer, and Coverage is trying to lean on it more heavily. The benefit is, you don't need to write the default excludes again (e.g. # pragma: no cover, and whatever may come in the future).

It's quite minimal; as you can see in https://coverage.readthedocs.io/en/latest/excluding.html#advanced-exclusion, the difference between the exclude_also instead of exclude_lines is that it doesn't override the default excludes, and instead appends to the list.