Interpret puppetdb_enabled="false" (string) as disabled

The default value of the puppetdb_enabled setting had been "false" (string)
causing the destroy handler to think it was always enabled, which would then
fail.  The default has been changed to a boolean, but also handle strings for
existing installations.

I could add DB migrations, but figured it's overkill.