Add /bigobj to MSVC compiles.

[clalancette]

Currently when building rosbag2_transport on Humble with Windows debug, it fails with the following error:

C:\ci\ws\src\ros2\rosbag2\rosbag2_transport\test\rosbag2_transport\test_play.cpp : fatal error C1128: number of sections exceeded object file format limit: compile with /bigobj [C:\ci\ws\build\rosbag2_transport\test_play__rmw_connextdds.vcxproj]

The advice there is pretty explicit; adding in the /bigobj flag should fix the compilation. We could alternatively fix this by splitting test_play.cpp into smaller pieces, but adding /bigobj is simpler. We also do this in a couple of other places, like https://github.com/ros2/rviz/blob/b30838530c1aee8f6ddcbd11db258fbd24e57935/rviz_default_plugins/CMakeLists.txt#L47 and https://github.com/ros2/system_tests/blob/2144c027383ff7c08c88c47aadaefcc701490d7c/test_communication/CMakeLists.txt#L16

[clalancette]

CI:

• Linux
• Linux-aarch64
• Windows
• Windows Debug

[MichaelOrlov]

I don't mind with changes from this PR it looks reasonable for me.
However, I am bit worry that Windows Debug job failed.
It seems failure is unrelated

launch_testing_examples\check_multiple_nodes_launch_test.py --- stderr: launch_testing_examples
Windows fatal exception: access violation

Thread 0x00001f00 (most recent call first):
  File "C:\Python38\lib\selectors.py", line 314 in _select
  File "C:\Python38\lib\selectors.py", line 323 in select
  File "C:\Python38\lib\asyncio\base_events.py", line 1823 in _run_once
  File "C:\Python38\lib\asyncio\base_events.py", line 570 in run_forever
  File "C:\ci\ws\install\Lib\site-packages\launch\utilities\signal_management.py", line 135 in run_background_loop
  File "C:\Python38\lib\threading.py", line 870 in run
  File "C:\Python38\lib\threading.py", line 932 in _bootstrap_inner
  File "C:\Python38\lib\threading.py", line 890 in _bootstrap

Thread 0x00001c60 (most recent call first):
  File "C:\ci\ws\src\ros2\examples\launch_testing\launch_testing_examples\launch_testing_examples\check_multiple_nodes_launch_test.py", line 127 in wait
  File "C:\ci\ws\src\ros2\examples\launch_testing\launch_testing_examples\launch_testing_examples\check_multiple_nodes_launch_test.py", line 57 in test_nodes_successful
  File "C:\Python38\lib\unittest\case.py", line 633 in _callTestMethod
  File "C:\Python38\lib\unittest\case.py", line 676 in run
  File "C:\Python38\lib\unittest\case.py", line 736 in __call__
  File "C:\Python38\lib\unittest\suite.py", line 122 in run
  File "C:\Python38\lib\unittest\suite.py", line 84 in __call__
  File "C:\Python38\lib\unittest\suite.py", line 122 in run
  File "C:\Python38\lib\unittest\suite.py", line 84 in __call__
  File "C:\Python38\lib\unittest\runner.py", line 176 in run
  File "C:\ci\ws\install\Lib\site-packages\launch_testing\test_runner.py", line 192 in _run_test
  File "C:\Python38\lib\threading.py", line 870 in run
  File "C:\Python38\lib\threading.py", line 932 in _bootstrap_inner
  File "C:\Python38\lib\threading.py", line 890 in _bootstrap

Although it might mask other failures.

[clalancette]

I think I'm going to go ahead and merge this one, even with the test failures. This clearly improves the situation (at least we can compile), and we can address the other failing tests separately.