Enable pylint's dangerous-default-value check

[garrison]

When I ran pylint in its default configuration, I noticed a few dangerous-default-value warnings in the new cut finder. I think it's worth adding this to our pylint configuration and fixing the existing issues in the code base. (Even though users aren't supposed to directly call this code, adding this to our config allows us to prevent similar dangerous defaults in places we do care about.)

[coveralls]

Pull Request Test Coverage Report for Build 8668017661

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 5 of 5 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.005%) to 95.438%

---

Totals
Change from base Build 8664308665:	0.005%
Covered Lines:	3452
Relevant Lines:	3617

---

💛 - Coveralls

[ibrahim-shehzad]

Interesting! I had to look at the examples given here to understand what the potential danger was but this makes sense now. I made a minor modification to one of the tests and a docstring, just to make sure everything was consistent. This looks good to me overall, thanks