Fix VMM tests

[leofang]

Description

follow-up of #1242
closes#1276

Checklist

• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[leofang]

/ok to test 3dd1bc5

[leofang]

Ah... On the self-hosted Windows runners we don't have MSVC, so CFFI would not work 😞

[github-actions]

Doc Preview CI
🚀 View preview at https://nvidia.github.io/cuda-python/pr-preview/pr-1277/
https://nvidia.github.io/cuda-python/pr-preview/pr-1277/cuda-core/
https://nvidia.github.io/cuda-python/pr-preview/pr-1277/cuda-bindings/
https://nvidia.github.io/cuda-python/pr-preview/pr-1277/cuda-pathfinder/
Preview will be ready when the GitHub Pages deployment is complete.

[kkraus14]

My 2c: having this OBJECT_ATTRIBUTE directly exposed to cuda.core doesn't make sense where I wonder if we can pull out the key functionality that is needed from it and support those more directly via args/kwargs to hide this as an implementation detail from users. If they need the low level functionality they can always reach for cuda.bindings.driver.

[leofang]

Discussed during the meeting, we want to hide this for now and raise an exception asking users to reach out to us if they use handle_type="win32". I'll prepare another PR to do this.