Convert-Bpf2Native.ps1 should add resource strings

Example (good case):
```
PS E:\ebpf-for-windows\build\x64\Debug> Get-ItemProperty .\EbpfApi.dll | fl

Directory: E:\ebpf-for-windows\build\x64\Debug

Name : EbpfApi.dll
Length : 4500480
CreationTime : 5/13/2022 9:02:00 PM
LastWriteTime : 5/13/2022 9:10:26 PM
LastAccessTime : 5/13/2022 9:10:26 PM
Mode : -a----
LinkType :
Target : {}
VersionInfo : File: E:\ebpf-for-windows\build\x64\Debug\EbpfApi.dll
InternalName: ebpfapi.dll
OriginalFilename: ebpfapi.dll
FileVersion: 0.0.0.1
FileDescription: eBPF For Windows User API dab48c27eafd03b08c5dd1c06c3188296c81451c
Product: eBPF for Windows
ProductVersion: 0.0.0.1
Debug: True
Patched: False
PreRelease: False
PrivateBuild: False
SpecialBuild: False
Language: English (United States)
```

Example (bad case):
```
PS E:\ebpf-for-windows\build\x64\Debug> Get-ItemProperty .\bindmonitor.sys | fl

Directory: E:\ebpf-for-windows\build\x64\Debug

Name : bindmonitor.sys
Length : 12648
CreationTime : 5/13/2022 9:02:08 PM
LastWriteTime : 5/13/2022 9:02:09 PM
LastAccessTime : 5/13/2022 9:02:47 PM
Mode : -a----
LinkType :
Target : {}
VersionInfo : File: E:\ebpf-for-windows\build\x64\Debug\bindmonitor.sys
InternalName:
OriginalFilename:
FileVersion:
FileDescription:
Product:
ProductVersion:
Debug: False
Patched: False
PreRelease: False
PrivateBuild: False
SpecialBuild: False
Language:

```

It would probably make sense to include info about the original file the PE image was generated from.

Start by reading Convert-Bpf2Native.ps1 and run it on the DLL and SYS examples shown in the issue. Trace how the generated PE images receive version metadata, then verify that the output includes resource strings and identifies the original input file, matching the displayed Get-ItemProperty fields.

Written by the indexing model from the issue text.