Trigger plan on new module version

[BSick7]

When a module contributor publishes a new module version, you must manually trigger plans that use those modules. When rolling out new infrastructure code, most users want any infrastructure changes to immediately plan (and sometimes apply) to the first environment in their pipeline.

Nullstone should allow a user to configure a block/application to trigger a plan with an optional auto-apply based on a branch.

By default, a block should set this off since most modules that users use come from the official Nullstone catalog.