Using furrr instead of pbapply and letting the user set the parallelization.

[ManonSimonot]

• {pbabbly} has been deleted from the package and replaced with {furrr} and {progressr}.
• all 'ncores' parameters have been deleted from the package: that implied changes in the compute_point_estimate() function that should be reviewed since I was not sure how this has to be done.
• a vignette has been created to tell the user how to set parallelization with {future}, {parallel} and {progressr}: modifications may be needed.

[astamm]

Thanks for the PR. It is important to benchmark to ensure that parallel processing speeds computation up. This can be done in the vignette that you created to further prove to users the benefits of using parallel computations.

The compute_point_estimate() function is a work-in-progress and did not work well even before your changes. You should clean the file to remove currently commented lines and add an issue to better work out the optimization problem that this function requires to solve.

[ManonSimonot]

The vignette has been updated with a time comparison between sequential and parallel processing.
The compute_point_estimation() function is clean and an issue is open for this matter.