Hard-coded check for presence of "prod" string in account alias is too restrictive

[krishnan-mani]

As documented in the README, aws-nuke refuses to run as soon as it detects the presence of the (substring) prod in the AWS account alias.

However, it is also not uncommon to use a string such as nonprod (!) in the alias for accounts that not in production use, and these are precisely the kinds of accounts one may want to use aws-nuke against, as they are used for experimentation.

Rather than be forced to fork the repo (to make a trivial change to remove the hard-coding), we are requesting that the user be allowed to specify a choice for this kind of safeguard.

This is currently an impediment to our intended use of aws-nuke

[sstoops]

I think this PR may address your concern: #983

[ikarlashov]

We have the same issue that OP described. It's not possible to nuke nonprod accounts. Also all accounts that have productivity or producer in the name won't be nuked.