Refactor == operator to support generic numeric equality

[yabuz87]

Summary

This update refactors '=='/3 to avoid any recursive structural equality checks and instead rely entirely on Prolog’s built-in optimized operators.

The implementation:

• Uses strict term equality (==/2) as the primary fast path
• Falls back to arithmetic equality (=:=/2) when both arguments are numbers
• Introduces no recursive traversal
• Preserves performance by leveraging built-in predicates only

This approach removes the performance concerns associated with recursive equality checking while maintaining clear and predictable semantics. Since no custom recursion is introduced, the change should not raise the benchmarking issues previously mentioned.

Feedback and suggestions are welcome.

[patham9]

This does not solve the issue, what if it is (1) and (1.0) in a list we are comparing with. Did you forget our discussion?