Prompt "are you sure?" before deleting .next directory with publish init command

[yousefamar]

Please select if your request is either something new or an enhancement

• Enhancement of an existing Feature.
• Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

• Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
• Lookup - Dendron's Lookup Command
• Views - Dendron Preview, Tree View, Side Panels in the UI
• Schema - Dendron Schemas
• Pod - Data import from / export to Dendron
• Publish - External Site Publish
• Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe

I ran dendron publish init absent-mindedly and it deleted an existing .next/ which had some stuff I needed.

Describe the solution you'd like

Would be cool if it didn't automatically delete .next/ or asked you if you're sure (y/n).

Describe alternatives you've considered

-

Additional context

🌱 checking if .next  directory exists.
🌱 .next directory exists
🌱 existing .next directory deleted.
...

[SeriousBug]

Thanks for the suggestion. The .next folder is generally "transient" and can be recreated, but I agree that init shouldn't blindly delete it.

[LukeCarrier]

As a heads up, this behaviour changed in #2162: dendron publish init will now first try to update the existing template, but if that fails the directory will be removed without confirmation.