Consider offering to the user to install flavors at the end of `hpal new`

[devinivy]

There is some concern noted originally here hapipal/boilerplate#85 that a user may be confused if they add a model after hpal new completes, but the server is still misconfigured. The fix would be to install a flavor first. Perhaps we can bake this into the hpal new process to help streamline setup and as an opportunity to educate new users what to expect next. One snag that we may run into is that an initial commit must be made before cherry-picking a flavor. Any thoughts?

[dcominottim]

Thanks for opening the discussion here! :)

Thinking about your comments on the original issue, perhaps we could think of something separate from hpal new? You made a good point about most things from the hapi ecosystem being optional (and customizable by means of the .hc.js file in the case of hapipal projects), which made me think that perhaps the solution lies in a new hpal command with semantics of "add a barebones config for this feature/module". I still need to look into hpal in more detail to see how things are currently being implemented.