Add unmatched push/pop warning

[Homaid]

Resolves #8209

Changes:

added a Friendly Error System (FES) warning to detect unmatched push() and pop() calls that can cause performance degradation and browser freezing.

What was added:

• Warning when push() is called more than 100 times without matching pop() calls within a frame
• Warning when pop() is called more times than push()
• Warnings are shown only once per sketch run to avoid console spam
• Uses the FES system for consistency with other p5.js error messages

Screenshots of the change:

PR Checklist

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

[Homaid]

Hii @davepagurek can you review this and let me know if anything needs to change thank you!!

[perminder-17]

Hi, in the screenshot when there's a loop of 100 push() calls without pop() calls, the friendly error message is showing something around 200. Is that expected? or it's something like showing the unmatched stack depth?

[Homaid]

Hii @perminder-17 i'm glad you mentioned this and yes, that's expected because the warning triggers when depth exceeds the threshold (100), and by the time it shows the warning (after frame 2), the depth is already 200!

[davepagurek]

Do you think the threshold needs to be 100, or should it just be > 0?

[Homaid]

i thought it will give some flexibility and only warns when it becomes a real problem, there is no downside of using >0. i will update it thank you @davepagurek