fix: account-blocklist deprecation message

[darkowlzz]

It logged account-blocklist as account-blacklist before.

For a config with account-blocklist

account-blocklist:
- "999999999999"

Before:

$ ./aws-nuke run -c nuke-cfg.yaml
WARN[0000] deprecated configuration key 'account-blacklist' - please use 'blocklist' instead  component=config
> aws-nuke - 3.0.0-dev - dirty
Do you really want to nuke the account with the ID XXXXX and the alias 'xxxxx'?
Do you want to continue? Enter account alias to continue.

After:

$ ./aws-nuke run -c nuke-cfg.yaml
WARN[0000] deprecated configuration key 'account-blocklist' - please use 'blocklist' instead  component=config
> aws-nuke - 3.0.0-dev - dirty
Do you really want to nuke the account with the ID XXXXX and the alias 'xxxxx'?
Do you want to continue? Enter account alias to continue.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.76%. Comparing base (6bcf973) to head (4946f2b).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #65   +/-   ##
=======================================
  Coverage   97.76%   97.76%           
=======================================
  Files          17       17           
  Lines        1072     1072           
=======================================
  Hits         1048     1048           
  Misses         13       13           
  Partials       11       11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ekristen]

@darkowlzz can you rebase when you get a minute this will fix the tests so that they pass.

[darkowlzz]

Rebased 🙂

[ekristen]

🎉 This issue has been resolved in version 0.17.2 🎉

The release is available on GitHub release 🚀