(#20121) Invoke chkconfig with --check on SuSE

On SuSE the `chkconfig` command needs to be passed the `--check` flag in order
to get exit codes that indicate if a service is enabled or not. Previously, we
were applying a regex to stderr but this was missing the case where the service
did not exist.

Ref: [#20121](https://projects.puppetlabs.com/issues/20121)
(maint) Fix failing puppet module build test

cd4d720 fixed the issue with `puppet module build` on Solaris, but did
not update the spec test to reflect the new command being executed.

This patch updates the spec test.
Merge branch 'fix_pmt_build'

* fix_pmt_build:
  (maint) Fix failing puppet module build test
Merge pull request #1602 from Sharpie/20121-fix-suse-chkconfig

(#20121) Invoke chkconfig with --check on SuSE
(maint) Update branch strategy to be the git flow process

Without this patch it's still a bit confusing how to deal with a bug fix
that is merged into stable.  The merge up process documented in
COMMITTERS requires us to reset the stable branch on a new release.

We can avoid this reset if we switch fully to the process described by
[git flow](http://nvie.com/posts/a-successful-git-branching-model/).
The major difference described in this commit is that bug fixes are
reset onto stable, then merged as-is into both `stable` and `master`
without a merge-up of stable into master or a rebase of the change set
back onto master.

This process avoids the reset, allows both `stable` and `master` to have
infinite lifetimes, and keeps the history clean and free of duplicate
commits.

[ci skip]