Add camera calibration to insights

CV.json has camera calibration to adjust for perspective. It also identifies near court from far court. That bit is gold. Can that migrate to insights?

The issue is that near court positional data is far superior to far court. Understandable. Everything is very compressed over there. The best margin of error I’ve achieved on far court is 4.3 feet, which is fine for getting a general idea where you are on the court, but there are metrics I want to track that require more precision. You get that on near court.

With a set of games I can say “only take positional data when the player is on the near court.” Then I can trust that data much more.