No setCameraPose method on AprilTagProcessor

This is an issue for future years/releasees of the SDK. There is no setCameraPose method for AprilTagProcessor objects. The setCameraPose method is only available on the builder. This means (AFAIK) that the only way to have multiple cameras in different positions on the robot is to have multiple AprilTagProcessors - one for each camera position. This also means you are enabling and disabling AprilTagProcessors when you switch cameras, which causes delays in the processor settling and providing AprilTag detections.

Since the setCameraPose only changes the parameters for calculating field position from the AprilTag pose, why not put the setCameraPose method on the AprilTagProcessor instead of the builder? That way you could have one AprilTagProcessor and keep it running (active), and just call setCameraPose with the corresponding camera position and orientation parameters when you switch cameras.

Start at the AprilTagProcessor and its builder, comparing where setCameraPose is currently exposed and how pose parameters are used. Review the SDK API and any existing tests for processor pose updates; done means one active processor can accept a changed camera position and orientation without separate processors or enable/disable switching.

Written by the indexing model from the issue text.