Use binary search to reduce time when initializing BezierCurve

[CacPixel]

Feature report check list

• What you want is not included in the latest snapshot version of fixRTM.
• You couldn't find same request in the issues.

Describe the feature

In original RTM, a very simple search method is used when initializing normalizedParameters: search the required result from the start of an array. It's too slow when the bezier curve is very long and it directly runs on client thread(when onChangeRailShape, editing lines) or server thread(when creating rails). Use binary search algorithm instead of the original one can reduce the time spent a lot.
I tested on my mod, 120ms->1ms when invoking initNP(), 400m long curve.

[CacPixel]

tested on recent commit of fixrtm, even if the rail is very long, it only takes 2~3ms, instead of hundreds of miliseconds(which lags the entire client and drops the fps to very low)
I added a ngtlog timer when testing to print the time consumed:

[20:38:23] [Client thread/INFO] [NGT]: initNP time:2ms
[20:38:23] [Client thread/INFO] [NGT]: initNP time:2ms
[20:38:23] [Client thread/INFO] [NGT]: initNP time:3ms
[20:38:23] [Client thread/INFO] [NGT]: initNP time:2ms
[20:38:23] [Client thread/INFO] [NGT]: initNP time:2ms
[20:38:24] [Server thread/INFO] [NGT]: initNP time:2ms
[20:38:24] [Server thread/INFO] [NGT]: [Marker] Start pos BlockPos{x=0, y=66, z=3} for BlockPos{x=0, y=66, z=3}
[20:38:24] [Server thread/INFO] [NGT]: [Marker] Start pos BlockPos{x=0, y=66, z=3} for BlockPos{x=-60, y=66, z=-57}

Tested on forge 2859, ngtlib 2.4.21, rtm 2.4.24, fixrtm latest commit(9eeff27)

[anatawa12]

implemented in #713