mitigated some modernize-use-auto clang-tidy warnings

[firewave]

No description provided.

[firewave]

This produces a lot of warning for iterators. We could switch to auto in cases where the type is actually explicit like cbegin() etc.. But for calls like find() it depends on the container and we might end up with an iterator which would undermine the intended constness.

It will most likely not be of any harm but I would prefer to enforce the constness if possible. That could be done using std::as_const() but that isn't available until C++17.

As the iterator case already yields a separate message this is treated as a different group of issues. So I will file a ticket about making this configurable.

[firewave]

I filed llvm/llvm-project#84324 upstream about the iterator issue.