Lint to suggest match instead of [...].contains

This is a common pattern from python that can be done more efficiently in Rust. Essentially, converting something from the form x in (a, b, c) to the Rust equivalent [a, b, c].contains(x) is not as ideal as match { a | b | c => ..., _ => () }.

This might not be as easily auto-fixable, as the code could probably be restructured better, but this is a good idea for a lint at least.

Anything that involves creating an array or slice of constants and immediately calling contains is a candidate.

Start from the proposed pattern in the issue body: an array or slice of constants immediately passed to contains. Review existing Clippy lint entry points and tests for similar collection or match suggestions, then define the supported cases and confirm completion by adding coverage for the recognized pattern and its diagnostic behavior.