[Windows] MediaPicker.CaptureVideoAsync keeps handle to file after capturing video

Description

Using MediaPicker.Default.CaptureVideoAsync on the Windows platform keeps a handle to the capture.mp4 that gets created in the cache of the app. This doesn't clear, even after closing and reopening of the app, so operations on that file, such as recursively deleting your cache directory, will cause an exception.

Steps to Reproduce

1. Consume the MediaPicker.Default.CapturePhotoAsync() somewhere in your app, following the example in the docs
2. Use code such as System.IO.Directory.Delete(FileSystem.CacheDirectory, true), to delete the captured media - see exception at that point due to file lock
3. Close the app and navigate to the cache directory in File Explorer and attempt to delete the file manually - see prompt the file is in use by another process.

In the repro project, launch it, click the button, record a video, then click the button again.

Link to public reproduction project repository

https://github.com/thomasphillipsgb/Windows-CaptureVideoAsync-Bug

Version with bug

9.0.40 SR4

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

Windows SDK 10.0.22000.0

Did you find any workaround?

Opening and closing the camera app forces the handle to be released.

Relevant log output

Start at the Windows implementation behind MediaPicker.Default.CaptureVideoAsync and compare its capture lifecycle with the repro project linked in the issue. Reproduce the second capture and Directory.Delete(FileSystem.CacheDirectory, true) failure, then verify the capture.mp4 handle is released so the cache file can be deleted after capture and app restart.