Update nuspec to place library files under nano TFM (netnano1.0)

[Copilot]

Nuspec was placing output files directly under lib\ and lacked a proper target framework dependency group for .NETnanoFramework1.0.

Changes

• Dependency group: Wrapped nanoFramework.CoreLibrary dependency in <group targetFramework=".NETnanoFramework1.0">
• File targets: Replaced five individual file entries (dll, pdb, pdbx, pe, xml) with a single wildcard entry under lib\netnano1.0

<!-- Before -->
<dependencies>
  <dependency id="nanoFramework.CoreLibrary" version="2.0.0-preview.35" />
</dependencies>
...
<file src="...\nanoFramework.System.Security.Cryptography.dll" target="lib\nanoFramework.System.Security.Cryptography.dll" />
<file src="...\nanoFramework.System.Security.Cryptography.pdb" target="lib\nanoFramework.System.Security.Cryptography.pdb" />
<!-- ... and so on for pdbx, pe, xml -->

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

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.

Work from the DEVELOP branch.

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud