Faulty conditional was evaluating whether the cropping parameter in config equals string "True", rather than boolean True. This lead to unintended false evaluation for cropping field with boolean value True.

In the original behaviour, cropping=None was interpreted as read cropping params from config. This is in contrast to most other occurrences (`video_inference`, `gui.tabs.analyze_videos`, `VideoIterator`), which interpret cropping=None as no cropping. This leads to potential conflicts.

This commit changes the behaviour for cropping=None, which is now interpreted as no cropping (like elsewhere).

For backwards compatibility, the default argument is changed to 'from_config' which follows prior behavior.

Bounding box positions were corrected by the crop margin, even when the output video is also cropped (which should not be the case). This leads to misplaced bounding boxes.

This commit fixes the unintended behaviour where bounding box positions are always corrected: i.e. bounding boxes are only corrected when cropping was used during video AND the output video is not cropped.

In prior implementation, whether to use cropping or not was determined by the cropping coordinates, rather than the boolean cropping flag in video metadata.

When metadata specifies cropping=False, now no cropping is applied.