bugprone-use-after-move: Support configuration for custom container + pointer types

[nelhage]

Bugzilla Link	37553
Version	unspecified
OS	All

Extended Description

The documentation states that “reinitialization” occurs if [among others]:

• clear() or assign() is called on the variable and the variable is of one of the standard container types basic_string, vector, deque, forward_list, list, set, map, multiset, multimap, unordered_set, unordered_map, unordered_multiset, unordered_multimap.

Please add a configuration option allowing users to specify additional custom container types with the same semantics. I'm programming against absl::InlineVector, and it is frustrating that .clear() on that type -- which in ~every other way behaves like std:vector -- does not satisfy this clang-tidy check.

Similar configuration for custom smart-pointer types and reset() would likely also make sense.