[Area-Build] Fix build for VS 16.10

[mykhailopylyp]

Summary of the Pull Request

What is this about:
After updating to VS 16.10 KBM module fails to build.
There are two issues:

• int can't be implicitly converted to DWORD. I'm not sure what is the reason behind it as both are 32-bit integers
• There are issues with initializing RemapBufferItem({ 0x41, 0x42 }. It produces an empty vector. I guess it's going to be fixed soon but we need to fix it to unblock master.

What is include in the PR:

How does someone test / validate:

Quality Checklist

• Linked issue: Unable to build the solution in VS 2019 16.10 #11545
• Communication: I've discussed this with core contributors in the issue.
• Tests: Added/updated and all pass
• Installer: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Docs: Added/ updated
• Binaries: Any new files are added to WXS / YML
  • No new binaries
  • YML for signing for new binaries
  • WXS for installer for new binaries

Contributor License Agreement (CLA)

A CLA must be signed. If not, go over here and sign the CLA.

[TobiasSekan]

* `int` can't be implicitly converted to `DWORD`. I'm not sure what is the reason behind it as both are 32-bit integers

I'm not sure, but i think
DWORD is always a 32-bit on Windows and int is platform specific (16-bit or 32-bit)

https://docs.microsoft.com/en-us/windows/win32/winprog/windows-data-types says

A 32-bit unsigned integer. The range is 0 through 4294967295 decimal.
This type is declared in IntSafe.h as follows:
typedef unsigned long DWORD;