Move the onClose python applogic methods in c++ LidarCoreManager.

* If you reached this commit for a line in `git blame`,
re-run the blame operation starting at the parent of this commit
to see older history for the content.

* If you reached this commit for a line in `git blame`,
re-run the blame operation starting at the parent of this commit
to see older history for the content.

* If you reached this commit for a line in `git blame`,
re-run the blame operation starting at the parent of this commit
to see older history for the content.

* If you reached this commit for a line in `git blame`,
re-run the blame operation starting at the parent of this commit
to see older history for the content.

* If you reached this commit for a line in `git blame`,
re-run the blame operation starting at the parent of this commit
to see older history for the content.

* If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content.

(cherry picked from commit 86019e1878f613d59481f2b4d9aa02126ab2de41)

Add sliders for translations and rotation updates, linked to lidar proxies to help manipulate the sensor data

[fix][control toolbar] set default mode to play mode ( and update button accordingly ) when going in stream mode

(cherry picked from commit 8bb4f504)

(cherry picked from commit 39982b00)

When the user try to move frame by frame, some frames were skipped. This was
due to the wrong play mode been set before calling GoToPrevious or GoToNext.
There was an additional issue when the user selected 'ALL Frame' in the
PlayerControlerToolbar.

The wrong enum has been use all over this file.

Remove `Custom` and restore `All Frame` mode.

The speed was not respected when opening a pcap. Despite being set to `x1`,
the data were playing as fast as possible.
This is due to vtkSMAnimationSceneProxy::UpdateAnimationUsingDataTimeSteps
which is called by the pqApplyBehavior

This happend only OSX because the dynamic cast didn't work as expected.
We suspect, it's because due to the proxy mechanism:
The proxy are generated by paraview, and for some reason the true class cannot
be identified.