Implemented VulkanDevice.Dispose

[jp2masa]

What does the pull request do?

Implemented VulkanDevice.Dispose, calling vkDestroyDevice.

What is the current behavior?

When using the Vulkan backend, at least 2 VkDevices are created, one for initialization and one for rendering. The initialization one is always leaked, because Dispose is called, but it is not implemented.

What is the updated/expected behavior with this PR?

• Debugging with RenderDoc works (it only works with one VkDevice per VkInstance)
• VkDevices are no longer leaked

How was the solution implemented (if it's not obvious)?

It's obvious

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

N/A

Obsoletions / Deprecations

N/A

Fixed issues

Fixes #15926

[avaloniaui-bot]

You can test this PR using the following package version. 11.2.999-cibuild0048857-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[cla-avalonia]

• All contributors have signed the CLA.

[jp2masa]

@cla-avalonia agree

[maxkatz6]

@jp2masa thank you. I wonder how useful is RenderDoc with Avalonia. Or do you use it for embedded 3d rendering?

[jp2masa]

Or do you use it for embedded 3d rendering?

Exactly.

[kekekeks]

Note that we still should be cautious with this, since we have to destroy any objects created with that device.