Skipped by default configuration stage may be not so useful

By default BuildStream omits configuration steps on subsequent builds for optimization purposes (https://docs.buildstream.build/master/developing/workspaces.html#incremental-builds). There is a command to overcome that, but actually this optimization does not seem useful at least at the initial stages of development, e.g. when adding new elements and changing configuration frequently. For instance, I often spend much more time to understand problems and to run necessary missed configuration steps, then I get from this optimization.

It would be great to have an ability to disable this optimization either globally or for the build command. Probably, it has sense to disable it by default and to enable it, say, via an extra command-line argument.

Start with the incremental-builds documentation and the build command's configuration-stage handling. Determine how the existing command to rerun skipped configuration works and whether the requested control belongs globally or on the build command; done means the optimization can be disabled as described, with the default behavior and command-line usage documented.

Written by the indexing model from the issue text.