Feature: `Prompt` Step type

[alex-way]

I think it could be useful to have a Prompt step type, which sets the value to a specified variable.

The main use case I'm thinking of is a confirmation prompt, likely when doing something dangerous. For example, rm -rf <dir>.

There could also be appetite to also allow free text input, or allow the user to select a value from a defined list.

Appreciate this could totally be out of scope though.

[dbanty]

We're using inquire for built-in prompts (things like asking for tokens and building changesets). We could definitely expose some of those types through new steps. It's probably best to only add things as folks need them so we don't have to worry about designing things before necessary. So, for this use-case, maybe we add a Confirm step which builds an inquire::Confirm? Would you want a custom message, or should we start with a generic default, like "Continue?" or something.

Also, particularly for confirm, would you also want a command-line option that auto-confirms? So if you run something like knope workflow-that-needs-confirmation -y it doesn't prompt.

[alex-way]

I think that would work perfectly, I wonder whether it should be a separate step or whether it should just be an additional argument within the workflow?:

[[workflows.steps]]
type = "Command"
command = "git switch -c release"
confirm = true

[dbanty]

Probably better to make it a standalone step, so folks can confirm before doing other built-in steps. Like, confirm before creating a pull request or a GitHub release.