RFR: 8320563: Remove D3D9 code paths in favor of D3D9Ex

[Lukasz Kostyra]

JFX minimum requirements guarantee 9Ex availability, so old non-Ex paths are no longer needed.

In multiple parts (ex. Mesh, Graphics, etc.) where the Device is acquired I changed the type to explicitly use `IDirect3DDevice9Ex`. Technically it doesn't matter much (`IDirect3DDevice9Ex` inherits `IDirect3DDevice` - it was leveraged to transparently use the Ex device in the backend) but now we don't have the non-Ex device, so that keeps it a bit more consistent and clear IMO.

Verified by running tests on Windows 11, did not notice any regressions. Unfortunately I have no way to test this on older systems.

-------------

Commit messages:
 - Remove isRTTVolatile native call
 - Remove non-Ex D3D9 device and object

Changes: https://git.openjdk.org/jfx/pull/1445/files
  Webrev: https://webrevs.openjdk.org/?repo=jfx&pr=1445&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8320563
  Stats: 138 lines in 18 files changed: 0 ins; 59 del; 79 mod
  Patch: https://git.openjdk.org/jfx/pull/1445.diff
  Fetch: git fetch https://git.openjdk.org/jfx.git pull/1445/head:pull/1445

PR: https://git.openjdk.org/jfx/pull/1445