Consider auto-filling nuspec elements in exported gallery packages

[glopesdev]

• README.md if there is one
• LICENSE if there is one
• Avoid using licenseUrl and iconUrl as they are not recommended anymore

[PathogenDavid]

For a bit of extra context/thoughts from DCM:

• Initially the context for this was being able to store metadata in a central place like many .NET projects do with Directory.Build.props
• We could also just have Bonsai remember the last settings used in the .bonsai folder (not ideal because we want people to use the Gallery or some evolution of it more readily.)
• Could live in a more authoritative evolution of Extensions.csproj (this would have to be a long-term solution, assuming we ever even do this)

---

An extra thought I had on the first one: If we want the metadata to be stored in a Workflow.bonsai or this central location (IE: Company name in Directory.Bonsai.nuspec, package name in Workflow.bonsai), how do we determine which one wins? For example some projects might want a single icon for all examples but others might do custom ones.

In a MSBuild context the project generally "wins" since Directory.Build.props is logically imported at the top of the project. However in a modern MSBuild context people are editing their projects by hand, so "use Directory.Build.props" is signified purely by the property missing. With Bonsai I think the expectation should more be that the GUI is able to be the only interface and it's slightly harder to have a clean interface that lets you have both. (Even if we say Directory.Bonsai.nuspec is an advanced user feature that has to be maintained with a text editor.)