Warn via FES when bezierOrder() receives a value other than 2 or 3

[harshiltewari2004]

Resolves #9079

Changes

bezierOrder() is documented as accepting 2 or 3 but validated nothing, so
out-of-range values reached the renderers and failed differently in each:
2D drew nothing, WebGL silently reinterpreted the shape as a quadratic, and
bezierOrder(1) threw a TypeError from inside p5.

fn.bezierOrder now emits a non-blocking FES warning when the order isn't
2 or 3. Renderer behaviour is unchanged — this only adds a message.

Per @davepagurek's preference on the issue, the check reads
p5.disableFriendlyErrors first, so a sketch with FES turned off does no
further work. order !== undefined is checked next so the getter form
(bezierOrder() with no argument) doesn't warn.

Non-numeric and non-integer values ('3', 2.5, null) also warn, since
they fail the same comparison.

The order-1 TypeError still occurs after the warning; the warning names
bezierOrder first, so the user sees the cause before the crash.

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@d3d2fbe/lib/p5.min.js

Published Packages

• https://pkg.pr.new/p5@d3d2fbe

Commit hash: d3d2fbe

Previous deployments

7a29e9e

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

2288cff

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

---

This is an automated message.

[perminder-17]

Looks good to me!