Fix MSVC build/runtime issues in oneVPL samples

[mav-intel]

Description

Fix MSVC build/runtime issues in oneVPL samples

Fixes VPL7-290, VPL7-291, VPL7-292, VPL7-293, VPL7-294

Type of change

Please delete options that are not relevant. Add a 'X' to the one that is applicable.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Sample Migration (Moving sample from old repository after completing checklist established)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Command Line
• oneapi-cli
• Visual Studio
• Eclipse IDE
• VSCode

Checklist for Moving samples:

Links and Details can be found in the samples WG Teams Files.

• Review sample design with domain reviewers https://github.com/oneapi-src/oneAPI-samples/wiki/Reviewers-and-Domain-Experts
• Implement coding guidelines and ensure code quality.
• Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
• Run jsonlint on sample.json to verify json syntax. www.jsonlint.com
• Adhere to readme template
• Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
• Enforce format via clang-format config file
• Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
• Review readme with Tom Lenth or Joe Oster. (GitHub User: JoeOster)
• Tested using Dev Cloud when applicable
• Implement fixes for ONSAM Jiras
• If you have new dependencies/binaries, inform Samples Project Manager Swapna R Dontharaju (@srdontha) or @JoeOster

[anjgola]

Trigger CI