ObjectTracker: expose tracking paramters; add force remove functionality

[SzabolcsGergely]

Updated object_tracker.py to reflect new functionality and API usage:

objectTracker.setOcclusionRatioThreshold(0.4)
objectTracker.setTrackletMaxLifespan(120)
objectTracker.setTrackletBirthThreshold(3)

config = dai.ObjectTrackerConfig()
config.forceRemoveID(idToRemove)
trackerConfigQueue.send(config)

Purpose

Specification

None / not applicable

Dependencies & Potential Impact

None / not applicable

Deployment Plan

None / not applicable

Testing & Validation

None / not applicable

[Copilot]

Pull Request Overview

This PR enhances the object tracking functionality by adding new properties and setter methods to better configure tracking behavior.

• Introduces new bindings for occlusion ratio threshold, tracklet max lifespan, and tracklet birth threshold.
• Adds a new object tracker configuration binding and updates the Python example to use a tracker configuration input node.

Reviewed Changes

Copilot reviewed 4 out of 6 changed files in this pull request and generated 1 comment.

File	Description
src/pipeline/node/ObjectTrackerBindings.cpp	Adds new property and setter bindings; however, there is a duplicate binding for "trackingPerClass".
src/pipeline/datatype/ObjectTrackerConfigBindings.cpp	Introduces bindings for the object tracker configuration.
src/DatatypeBindings.cpp	Registers the new object tracker configuration binding to the callstack.
examples/ObjectTracker/object_tracker.py	Updates the example pipeline to include tracker configuration parameters and handling.

Files not reviewed (2)

• CMakeLists.txt: Language not supported
• depthai-core: Language not supported

[Copilot]

Duplicate binding for 'trackingPerClass' detected. Please remove the duplicate line to avoid potential runtime issues or unexpected behavior.

Suggested change

.def_readwrite("trackingPerClass", &ObjectTrackerProperties::trackingPerClass, DOC(dai, ObjectTrackerProperties, trackingPerClass))

[moratom]

Any specific reason to have that condition here?
The UX seems better without it to me, since I presume you often want to prematurely remove the LOST tracklets.