Add objective integration tests for all example_ws configs

[rlpratt12]

Summary

• Add objectives_integration_test.py to 11 config packages (kitchen_sim, april_tag_sim, grinding_sim, dual_arm_sim, factory_sim, hangar_sim, kinova_sim, space_satellite_sim, space_satellite_sim_camera_cal, mock_sim, multi_arm_sim)
• Each test auto-discovers objectives via SystemConfigParser and runs them with per-config skip lists for user-input/ML/GPU objectives
• New objectives are automatically tested — if one requires skipping, CI fails and the PR author adds it to the skip list (fail-safe design)
• Add CI matrix job to run each config's tests in parallel via the existing workspace_integration_test reusable workflow
• Add missing ament_cmake_pytest + moveit_pro_test_utils test deps across all configs (including existing lab_sim)

Known TODOs

• Skip lists are best-guess based on objective names/XML analysis — need to validate with actual CI runs
• The existing integration-test-in-studio-container job still runs all tests including these, causing double-runs. Consider adding --packages-skip for config packages to that job
• 600s timeout may need tuning for configs with many objectives (e.g. lab_sim has 80)
• Cancel objectives sets are empty for new configs — looping objectives may need to be identified and added

Test plan

• All 12 test files parse correctly with valid Python syntax
• Skip list objective IDs verified against actual main_tree_to_execute XML attributes — all match
• CMakeLists.txt and package.xml changes follow existing lab_sim pattern
• Run integration tests for mock_sim (simplest, no skips) to validate end-to-end
• Run integration tests for a config with skips (e.g. kitchen_sim) to validate skip behavior

🤖 Generated with Claude Code

[JWhitleyWork]

Is a good start but needs some tweaking.

[JWhitleyWork]

The downside to doing this with a matrix is that it launches a separate Github Actions runner for each invocation of the matrix. If we do these all as a single colcon test --packages-select <list_of_packages>, many of them can still be run in parallel but we only spin up an instance, install dependencies, clone stuff, etc. once. Also, we should be doing this test for at least Humble and Jazzy (in a matrix because they are completely different environments).

[JWhitleyWork]

10 minutes? We usually give 10 minutes for all of colcon test. Does it actually take anywhere near this long?

[rlpratt12]

@JWhitleyWork I realistically don't have time to prioritize this any time soon, and I don't think you do either. WDYT: is this worth handing off (maybe have Shaur take over?), or leave it sit for now with the risk of it going stale, or just close this PR and let someone restart the work when there's a new ticket/priority to do this? (or other suggestion?)

[JWhitleyWork]

I think this is very worthwhile. We have very few tests on the example workspace and no real integration tests. I think @shaur-k would be the perfect person to work on this as most of the issues here are with CI changes (the current failures using the external workflow, matrix vs non-matrix, etc.). Probably for next sprint.