Update nuspec to place library under nano TFM

[Copilot]

The nuspec file was placing assemblies directly under lib\ and declaring a flat dependency instead of targeting the .NETnanoFramework1.0 TFM.

Changes

• Dependency group: Wrapped <dependency> in <group targetFramework=".NETnanoFramework1.0"> to correctly declare the TFM-scoped dependency
• File target path: Consolidated five individual file entries into a single wildcard entry targeting lib\netnano1.0

<!-- Before -->
<dependencies>
  <dependency id="nanoFramework.CoreLibrary" version="2.0.0-preview.35" />
</dependencies>
...
<file src="...\nanoFramework.System.Text.dll" target="lib\nanoFramework.System.Text.dll" />
<file src="...\nanoFramework.System.Text.pdb" target="lib\nanoFramework.System.Text.pdb" />
<!-- ...3 more entries -->

<!-- After -->
<dependencies>
  <group targetFramework=".NETnanoFramework1.0">
    <dependency id="nanoFramework.CoreLibrary" version="2.0.0-preview.35" />
  </group>
</dependencies>
...
<file src="nanoFramework.System.Text\bin\Release\nanoFramework.System.Text.*" 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.

Description

</issue_description>

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

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[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