fix: add no_log and harden gitignore

[stevefulme1]

Summary

• Security: no_log: true added to tasks handling credentials (aap_subscription.yml, aap_seed/main.yml, mtv_query_inventory.yml, install.yml, _storage.yml, _perform_operation.yml) to prevent secret leakage in Ansible logs
• Security: .gitignore hardened — added *.pem and *.key exclusions
• Docs: Standardized CODE_OF_CONDUCT.md, SECURITY.md, and license reference formatting
• Removed COPYING file (duplicate of existing LICENSE)

Original CI workflow fixes (gitleaks.yml shell injection, slack-pr-notifications.yml pull_request_target) are no longer applicable — those workflow files were removed from main in subsequent upstream commits.

Test plan

• Rebased on latest main
• COPYING file removed per reviewer feedback
• Verify credential values not visible in ansible output logs
• Verify .gitignore excludes *.pem and *.key files

[spyrexd]

Does this supersede #31 ?

[sabre1041]

@stevefulme1 this looks good. Only outstanding item is that there is a COPYING file that appears to be almost exactly the same as the LICENSE. One we resolve this discussion, we should be able to integrate these changes

[stevefulme1]

@sabre1041 Done — COPYING removed, rebased on latest main, and updated the PR description to reflect current scope (the original CI workflow files no longer exist upstream so those fixes dropped off naturally during rebase).

Sorry about the delay — I thought I had already addressed this!

[sabre1041]

@sabre1041 Done — COPYING removed, rebased on latest main, and updated the PR description to reflect current scope (the original CI workflow files no longer exist upstream so those fixes dropped off naturally during rebase).

Sorry about the delay — I thought I had already addressed this!

we're so close! PR title is now too log (its always something....)

[stevefulme1]

@sabre1041 Shortened the PR title to fix: add no_log and harden gitignore — dropped the (security) scope to match the repo convention.

@burigolucas Added the Security Policy link to the README Documentation section. Thanks for the catch!