Feature request: Guard against == for float comparison

I'm not sure if this is doable from ruff's side as this might need optional static typing (mypy for example).

I could think of the following cases where == should be discouraged (or avoided altogether as it's pretty unreliable, I cannot think of much use cases we need such comparison):

# directly compare floats
1.0 == 1.0 + 1E-8

# floats generated by evaluation
x = 1 / 3
if x == 0.333:
    do something

# sequence of floats
[1.0, ] == [1.0 + 1E-8, ]

# use `in` to check membership
0.0 in [0, 1, 2]