tests: fix three stale assertions

- multicamnode: type_id() assertions called the method on dyn
  NodeBehavior, which method resolution routed to std::any::Any's
  TypeId::of — qualify via NodeBehavior::type_id so the trait method
  (the &str node type id) is compared
- procpool: the per-worker GPU budget grew a security headroom (×2)
  for the CUDA-OOM flood; the two budget tests now assert against the
  real formula (2 GiB + 256 MiB at 1080p24, 2 workers at 4K/24 GiB)
- cli info fixture: the fixture runs 29.97 fps; the assertion expected
  30/1 (stale from the older fixture)

crates/oak-cli/tests/cli.rs

@@ -162,7 +162,7 @@ fn info_on_the_fixture_prints_the_project() {
 	assert!(stdout.contains("Modified: no"), "{stdout}");
 	assert!(stdout.contains("Sequences: 1"), "{stdout}");
 	assert!(stdout.contains("[0] \"Fixture Sequence\""), "{stdout}");
-	assert!(stdout.contains("frame rate: 30/1 (30.000 fps)"), "{stdout}");
+	assert!(stdout.contains("frame rate: 30000/1001 (29.970 fps)"), "{stdout}");
 	assert!(stdout.contains("Footage: 1"), "{stdout}");
 	// The C++ fixture stores the footage path relative to the project;
 	// the CLI resolves it against the project directory and reports it