Allow to specify miter limit and arc tolerance for polypath offsetting

[Xrayez]

Enhances #28987.
Closes #29886.

Recently I've been thinking that exposing miter limit and arc tolerance parameters for polygon/polyline inflating/deflating would be useful. I questioned whether it's reasonable to add those until this question/request was raised.

These parameters are added as default and reflect the defaults in ClipperOffset which is used internally (the only parameters which were missing).

[Zireael07]

Is that only for graphics, or can I obtain the offset path as Path2D or Vector2Ds? Just curious.

[Xrayez]

@Zireael07 the result is always an array of actual Vector2 vertices representing polygons/polylines, so you can do whatever you like with those (including drawing), think about it as core functionality. These methods could as well be integrated into "front-end" nodes like Path2D/Polygon2D/NavigationPolygon2D under the hood in the future.

[Xrayez]

Not sure about arc_tolerance parameter, I didn't see much of a difference in approximation, perhaps it's somehow related to requirement to scaling points before clipping. fixed. It can be dropped so that core/method_bind_ext.gen.inc wouldn't have to be included which would bloat the engine's binary size to my knowledge (if that's even a concern). resolved with workaround in #29758 (comment).

[Xrayez]

Removed core/method_bind_ext.gen.inc to avoid engine binary size bloat.

It's possible to configure arc tolerance when using offset_polygon_2d but not offset_polyline_2d because of limited default number of arguments used for binding (5, need 6!).

The above inconvenience can be remedied by including core/method_bind_ext.gen.inc but then again it could potentially bloat the binary size somewhat (if that's what concerns reduz).

[Xrayez]

Closing, see #36369 which should solve all mentioned limitations.