fix(signature): gate onChange emission behind requireAccept flag

[DevRushd]

Description

The end() stroke handler in SignatureCapture was emitting onChange(dataUrl) on every stroke regardless of the requireAccept prop. This allowed parent components to receive and commit the signature before the user pressed the "Accept" button, bypassing the approval gate entirely.

Fix

• The end callback now only calls onChange when requireAccept is false or undefined.
• When requireAccept is true, only the explicit "Accept" button click handler (handleAccept) emits the data URL.
• Added requireAccept to the end callback's dependency array for correctness.

Testing

• With requireAccept={true}: signatures are only committed via the Accept button.
• With requireAccept={false} or omitted: signatures emit on every stroke as before (no breaking change for existing callers).

Closes #1040

[drips-wave]

@DevRushd Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[RUKAYAT-CODER]

Thank you for contributing to the project.