Attribute Compare: Use the most complex data type instead of the least

Optimize comparisons by squaring threshold first

Merge branch 'master' into geometry-nodes-point-separate-node

Geometry Nodes: Support equality operations with all data types

Testing equality of vectors can't be done properly if they are implicitly
converted to float before-hand. This adds a lot of boilerplate code to
the node, maybe that can made more elegant in the future, but it's not
so complicated anyway.

Geometry Nodes: Add a method to find the lowest complexity attribute

For the attribute comparison node, it makes sense to read both input
attributes implicitly converted to the same data type. But the choice
of which of the two data types to read with is somewhat arbitrary.
This commit adds a utility function to choose the least "complex" data
type as a lowest common denominator, to make that choice less arbitrary
, and to support other needs in the future.

Geometry Nodes: Add utilities for getting an attribute's data type

With the previous helper function in this file you had to know the data
type you wanted for the input attribute before requesting it. This adds
another utility function for getting the data type without building the
attribute. The attribute's can be requested later after doing some
logic to figure out the right data type to read.

No functional changes in this commit.

Use new get_input_attribute abstraction

Merge branch 'master' into geometry-nodes-point-separate-node

Support meshes in addition to point clouds

Use text for comparison RNA enum items

Merge branch 'master' into geometry-nodes-point-separate-node

Merge branch 'master' into geometry-nodes-point-separate-node

Review feedback: Only move pointcloud, use numbers for naming

Merge branch 'master' into geometry-nodes-point-separate-node

Merge branch 'master' into geometry-nodes-point-separate-node

Geometry Nodes: Attribute compare node

This node reads two input attributes as floats and allows for basic
element-wise comparison operations. Like the attribute math node,
it's also possible to switch to using floats as inputs. This node can
be combined with the point separate node for more flexibility on which
points to separate out.

I used the same abstractions that the attribute math node uses in this
commit, assuming that makes sense.

Geometry Nodes: Refactor and change point separate node

The threshold input is unecessary with an "attribute compare"
node before this one, or with attribute rounding. So to remove some
complexity it is removed, and a boolean input attribute is used instead.

For the implementation, the existing code becomes a bit more specific
to point cloud data, because I'm realizing that mesh separate is quite a
different problem, and it doesn't make sense to force the same code
to be able to solve that too.

Geometry Nodes: Add boolean type to random attribute node

Geometry Nodes: Add a boolean attribute data type

Merge branch 'master' into geometry-nodes-point-separate-node