feat: component generator

[joshgummersall]

Introduces a component generate that scaffols empty and dialog-based bot component projects.

[tracyboehrer]

Should restructure to accommodate Dotnet. Other thoughts: What about based on component type? For example action vs trigger vs etc. In this PR, "action" would be what is called "dialog". Structure by platform and type. The question I have is what to put into the template. Putting multiply-dialog means the dev would always have some deleting and renaming. We could instead provide a Dialog subclass, with BeginDialog stubbed out (probably just with a TODO comment). This gets a little harry with triggers since those can be different. The readme's for each would provide guidance on next steps (links and whatnot).