Fix bug: distance filtering resulting in unmatched tracking ids

[a1600012888]

Hi, I fixed a bug in the post processing step inNuScenesTrackDataset._format_bbox.

This bug will produce mis-matched tracking indexs, results in a large drop in AMOTA, but leaves the RECALL not changed too much.

The bug is cuased by https://github.com/a1600012888/MUTR3D/blob/c2fde4eb43ace2bb80dd8ce40dd6afcd30043f08/plugin/track/dataset.py#L871 https://github.com/a1600012888/MUTR3D/blob/c2fde4eb43ace2bb80dd8ce40dd6afcd30043f08/plugin/track/dataset.py#L588 When I removed the boxes that are out of the range, the tracking id need to be changed too.
Now I merge the tracking id, score into the new Class NuScenesTrackingBox: https://github.com/a1600012888/MUTR3D/blob/main/plugin/track/dataset.py#L796. Then the mismatch of tracking ids caused from removing boxes is fixed.