STYLE: suppress false positive pylint findings for 'not-an-iterable'
- [ x] addresses one of the identified issues in  #48855 

Disabled pre-commit Pylint checks for `not-an-iterable` in `pyproject.toml`, found a few identified problems, all of which appear to be false positives.

thanks for working on this - not overly keen on adding lots of inline comments, if these are all false positives and it's not easy to address them then I think it's ok to not turn off this check

if somewhere in the code there is iteration over something non-iterable, the tests should catch that anyway > thanks for working on this - not overly keen on adding lots of inline comments, if these are all false positives and it's not easy to address them then I think it's ok to not turn off this check

Makes perfect sense.    I've moved on to another line item off the chart -- but if there's a "better" way that Pylint wants developers to handle iterables in these cases, I'm very curious to figure that out.
 Apparently my branch had fallen behind `main` so far that when I synced it in Github interface, I chose wrong button and closed it?

Anyways, I have an idea that I'm testing locally now, if it works, I'll reopen the PR.
 OK, pylint apparently assumes if you take a slice of something, it must be an iterable.

Only suppressed two warnings in one file, but in that function it's already got a `TODO` to refactor/combine with function from another file. I think having to do `[:]` to get around this warning would be unclear to contributors - I don't think this particular error message helps us avoid bugs that wouldn't be caught by the test suite, so I think we can just keep it turned off > I think having to do [:] to get around this warning would be unclear to contributors 

I think having to do `[:]` to suppress this raises questions about the pylint parser.

