Need a new tools archtype for ci

We have some tools that we would like to publish that aren't SDKs from the dotnet repo. Typically these only need to go to the azure dev feed and not public nuget and have slightly different patterns than sdks. Currently we are using the sdk archtype but would like a specialize archtype to use instead.

Locate the existing SDK archetype in the dotnet tooling and trace how it packages and publishes tools. Compare those patterns with the requested Azure Dev feed-only workflow and the differences from public NuGet publishing. Done means a distinct archetype exists for these tools and supports the intended feed and packaging behavior.

Written by the indexing model from the issue text.