Fix additional Ruff issues

[brianhelba]

A few of these are slightly bigger refactors, so the easiest way to review is probably commit-by-commit.

[brianhelba]

@BryonLewis @BryonLewis FYI, regarding boolean-type-hint-positional-argument, the essence of the rule is that positional boolean parameters are risky, but keyword boolean parameters are fine. Generally, the easiest way to resolve this is to just put the boolean behind a keyword-only syntax (e.g. def foo(*, bool_flag).

On the calling side, for boolean-positional-value-in-call, note that most of BatAI is already doing a great job with using a keyword syntax when passing boolean arguments, so very little change was needed.

[BryonLewis]

Thanks for organizing this by commit.
I went through and everything seemed clear to me.

Also, thanks for cleaning up my inconsistent casing. Jumping between Vue and Django can get me tripped up with camelCase vs. snake_case. I’ll keep a closer eye on that (the ruff rules not being blocked should force me to now).

[brianhelba]

Indeed, no need to think about such minor style stuff anymore. Ruff's your backstop.