fix early type checks for comparison/logical ops in binaryOpNode

[skyyash]

Resolves #8445

Changes:

• add early type validation for comparison and logical operators in binaryOpNode.
• ordering operators (<, <=, >, >=) are now rejected when either operand is a vector, matching glsl rules.
• equality and logical operators also get matching dimension/base-type checks.
• errors are thrown via the existing fes helpers.

PR Checklist

• npm run lint passes
• Inline reference is included / updated
• Unit tests are included / updated

[p5-bot]

Continuous Release

CDN link

• https://raw.esm.sh/pr/p5@6879d00/lib/p5.min.js

Published Packages

• https://pkg.pr.new/p5@6879d00

Commit hash: 6879d00

Previous deployments

e85a6e6

• https://raw.esm.sh/pr/p5@e85a6e6/lib/p5.min.js
• https://pkg.pr.new/p5@e85a6e6

---

This is an automated message.

[perminder-17]

Hi, thanks for your work on this! Do you think it would be worth adding two more cases?

1. Comparing two boolean values using <, etc. such as a < b where both a and b are booleans.
2. Comparing a boolean with a number using equalTo() or notEqual().

Both are invalid in GLSL, so catching them early with a strands error would be helpful? what do you think