Fix: Coerce string coordinates to numbers in boundsPoint function #278

[DoiMayank]

This pull request addresses issue #278, where path.bounds should return numbers even when input coordinates are strings.

I have modified the boundsPoint function to coerce input coordinates to numbers. I tested the changes, and they successfully return numerical bounds for both string and number inputs.