Ensure credentials are not being stored or captured

🗣 Description

Minor revision to configure all campaigns to not allow either credentials or passwords to be captured by Gophish.

💭 Motivation and context

Discussing with Kelly Theile and the PCA team, we discussed if passwords are being stored in plaintext (#52) and we were informed that we are not allowed to receive any credentials in any form (plaintext or encrypted) for legal reasons. Credentials must be dropped by the landing pages. This change ensures that no credential or password data is captured.

In addition, setting the capture credential and password boolean values was done in one place, before being repeated on each branch of execution.

Closes #52

🧪 Testing

This was tested by bringing the code changes into our LiPCA process and checking that the campaigns created afterwards were no longer configured to capture submitted data. After setting capture credentials to false, the checkbox in the Gophish GUI for capture submitted data is no longer set.

✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
[x] All new and existing tests pass.

cisagov / gophish-tools