pymavlink: deselect new v2.4.50 tests hitting the sdist fixture gap

test_context_manager.py's two ContextManagerTest cases (test.BIN) and
test_mavgen_typescript.py's only test (snapshottests/resources/common.xml)
are new in 2.4.50 and hit the same upstream sdist-packaging gap already
worked around for test_mavlogdump.py/test_mavxml.py/RallyTest/FenceTest:
the fixture files exist in the git checkout but upstream's sdist only
picks up tests/*.py, so cibuildwheel's sandboxed run (which reaches the
sdist's tests/ directly, no CIBW_TEST_SOURCES staging involved) gets a
FileNotFoundError for the fixture path.

Author: luhenry

.github/workflows/build-pymavlink.yml

@@ -146,11 +146,17 @@ jobs:
         # an earlier test file importing it first (with MAVLINK20 unset) leaves the
         # wrong dialect cached for the rest of the pytest run. Everything else in
         # the suite is self-contained and order-independent.
+        # v2.4.50 added two more tests that hit the same sdist gap: test_mavgen_typescript.py's
+        # only test reads tests/snapshottests/resources/common.xml, and
+        # ContextManagerTest.test_dfreader_binary/test_mavlink_connection_dataflash (in
+        # test_context_manager.py, alongside the fixture-free test_mavfile) read test.BIN.
         CIBW_TEST_COMMAND: >-
           python -m pytest {package}/tests
           --ignore={package}/tests/test_mavlogdump.py
           --ignore={package}/tests/test_mavxml.py
-          -k "not RallyTest and not FenceTest and not (MAVWPTest and test_save)"
+          --ignore={package}/tests/test_mavgen_typescript.py
+          -k "not RallyTest and not FenceTest and not (MAVWPTest and test_save)
+          and not (ContextManagerTest and (test_dfreader_binary or test_mavlink_connection_dataflash))"
       run: |
         set -eux