Consume wasm targets and metadata from the .NET Wasm SDK

[javiercn]

• We need to consume a target that does all the work to compute the list of files for the app.
  • During build
  • During publish
  • Independent of the gesture the user did (native compilation, linking enabled/disabled, etc.)
• We need to change the file names, paths, etc. to make them suitable to our layout.
• We need to add any information we want to include in mono-config.json
  • During build
  • During publish
• We need to implement our customizations for the deployment layout on top of the Webassembly provided extensibility points.

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

Closing as the Runtime team has handled this already.