use grpc++ instead of grpc++_unsecure

With the recent grpc bump, grpc causes troubles when both grpc and grpc_unsecure are loaded by the same binary.
Here, it is the case when StfSender and StfBuilder load the OccLite plugin (which uses grpc).
This change fixes both and allows them to be controlled by ECS again, tested on a VM setup with FLP suite.

I do not know if it might break DataDistribution in some other context, I hope that anyone reviewing it may know...

Fix compilation with boost 1.87

Make it compile with C++20 and protobuf 29.x

Bump spdlog version to v1.15.1

optionally store min-max raw TF range beyond random percentage

add SubTimeFrameFileSink options
--data-sink-stf-min-id <int (def=-1)>
--data-sink-stf-max-id <int (def=-1)>
to force storage of TFs with ID matching this limits (on top of
eventual random storage)

Fix compilation issue with CMake >= 3.28

By forcing make install -j1 for jemalloc library.

More fixes for fmt 10.1.1

Allow building with latest fmt

Improve error handling of 99283b6, throw only in case of TfBuilder no…

…t TfScheduler

Throw in case an FLP cannot connect, Now we have nmin, and in any cas…

…e, a dead FLP should break the run