[clang-tidy] Make `readability-use-anyofallof` check suggest usage of 'std::none_of'

[vbvictor]

Currently, we only diagnose suggestions with std::all_of, std::any_of.
I think we can add some heuristics to print to suggest for std::none_of too.
E.g. given this code:

for (auto E : S1)
  if (S2.count(E) == 0)
    return false;
return true;

It's arguably better to write none_of than any_of:

// we did't change predicate at all
return std::ranges::none_of(S1, [&S2](const auto& E) { return S2.count(E) == 0; });
// we changed predicate to '!='
return std::ranges::all_of(S1, [&S2](const auto& E) { return S2.count(E) != 0; });

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: Baranov Victor (vbvictor)

Currently, we only diagnose suggestions with `std::all_of`, `std::any_of`. I think we can add some heuristics to print to suggest for `std::none_of` too. E.g. given this code:

for (auto E : S1)
  if (S2.count(E) == 0)
    return false;
return true;

It's arguably better to write none_of than any_of:

// we did't change predicate at all
return std::ranges::none_of(S1, [&S2](const auto& E) { return S2.count(E) == 0; });
// we changed predicate to '!='
return std::ranges::all_of(S1, [&S2](const auto& E) { return S2.count(E) != 0; });

[LegalizeAdulthood]

Does this imply that the check name will change? That could break a bunch of config files

There might be a better more generic check name and the existing check name can be aliased to the generic name.

[vbvictor]

Does this imply that the check name will change? That could break a bunch of config files

I don't think we need to change check name for this piece of functionality. Those 3 functions are usually grouped together so I hope it will be obvious for users to understand that none_of is also included.