Fixes #37666 - Fix Candlepin reset in reset rake task

[chris1984]

What are the changes introduced in this pull request?

• With the recent changes to Candlepin and cpdb we forgot to update the reset rake task

basically, instead of cpdb --create --schema-only you need to be now running cpdb --create  (--schema-only no longer exists), 

instead of cpdb --update the new command is now cpdb --update-schema  (although, cpdb --update
may still work, because bash knows --update is start of --update-schema)

• Instead of using runuser postgres cpdb can create and drop the database for us, so switched to that for all native candlepin db actions.

Considerations taken when implementing this change?

• Make sure the Candlepin database gets recreated still

What are the testing steps for this pull request?

• Check out PR
• Reset your devel box bundle exec rake katello:reset --trace
• Verify you do not see the error message anymore

[ianballou]

Working well for me, just one rubocop issue.

will ack after rubocop's fixed

[chris1984]

@ianballou updated

[ianballou]

Looks good and works!

[evgeni]

Out of curiosity, why don't you use the reset feature of the installer? It has all the same bells and whistles and is actually tested regularly to do the right thing?

[chris1984]

Out of curiosity, why don't you use the reset feature of the installer? It has all the same bells and whistles and is actually tested regularly to do the right thing?

@evgeni I can make a PR to update the katello developer guide on the foreman.org to use the installer instead. I still think we should keep this one as well, because there are times for example on 1 dev box I have where it's setup for provisioning and if I don't pass all the prov params, it does not remember them. I only see this with the katello-devel scenario not on production. I guess I could pass them all with the --reset-data param but still think it's valid to keep this one too.