Update nuspec to place library files under nano TFM

[Copilot]

Library files were being placed under lib\ without a target framework moniker, and dependencies lacked a targetFramework group — both required for correct NuGet TFM resolution in nanoFramework projects.

Changes to nanoFramework.System.Device.Wifi.nuspec

• Dependencies: Wrapped all <dependency> entries in a <group targetFramework=".NETnanoFramework1.0"> element
• Files: Replaced five individual file entries (.dll, .pdb, .pdbx, .pe, .xml) with a single wildcard entry targeting lib\netnano1.0

<!-- Before -->
<dependencies>
  <dependency id="nanoFramework.CoreLibrary" version="2.0.0-preview.35" />
  ...
</dependencies>
<files>
  <file src="...\System.Device.Wifi.dll" target="lib\System.Device.Wifi.dll" />
  <file src="...\System.Device.Wifi.pdb" target="lib\System.Device.Wifi.pdb" />
  ...
</files>

<!-- After -->
<dependencies>
  <group targetFramework=".NETnanoFramework1.0">
    <dependency id="nanoFramework.CoreLibrary" version="2.0.0-preview.35" />
    ...
  </group>
</dependencies>
<files>
  <file src="System.Device.Wifi\bin\Release\System.Device.Wifi.*" target="lib\netnano1.0" />
  ...
</files>

Pattern follows the reference implementation in nanoframework/System.Device.Adc@aab7bca.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update nuspec to place library under nano TFM</issue_title>
<issue_description>### Details about task
Most of the nuspec files are not using the correct location to place the files.
Files (DLL, PE, PDBX and XML for IntelliSense) should be placed under "lib\netnano1.0" (currently are being placed under "lib" only.
Also they should declare a dependency group for ".NETnanoFramework1.0" target framework.
At the same time those still naming the various file types should use a wildcard instead (e.g. "...\Release\mscorlib.*).
The correct pattern should be (take this nuspec as sample):
nanoframework/System.Device.Adc@aab7bca

Do not change anything else on the nuspec file.

Description

</issue_description>

Comments on the Issue (you are @copilot in this section)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.