ci: run bindings examples via pytest entrypoint

Analysis:
- examples were invoked via `python -m pytest` from within `cuda_bindings`
  so the repo checkout was on sys.path and imports resolved to the source tree
- `setuptools_scm` generates `cuda/bindings/_version.py` only in the built wheel,
  so the source tree lacks this file and `from cuda.bindings._version import __version__`
  fails during example collection
- running `pytest` via the installed entrypoint avoids CWD precedence and keeps
  imports coming from the installed wheel, which includes the generated version file

Change:
- switch Linux and Windows example steps to call `pytest` entrypoint

Author: rwgk

.github/workflows/test-wheel-linux.yml

@@ -261,7 +261,7 @@ jobs:
           LOCAL_CTK: ${{ matrix.LOCAL_CTK }}
         run: |
           pushd cuda_bindings
-          ${SANITIZER_CMD} python -m pytest -ra -s -vv examples/
+          ${SANITIZER_CMD} pytest -ra -s -vv examples/
           popd
 
       - name: Run cuda.core tests

.github/workflows/test-wheel-windows.yml

@@ -234,7 +234,7 @@ jobs:
         shell: bash --noprofile --norc -xeuo pipefail {0}
         run: |
           pushd cuda_bindings
-          ${SANITIZER_CMD} python -m pytest -ra -s -vv examples/
+          ${SANITIZER_CMD} pytest -ra -s -vv examples/
           popd
 
       - name: Run cuda.core tests