Implementing Timeout Feature on S3

[james03160927]

Description

Fixes https://github.com/gruntwork-io/cloud-nuke/issues/417

TODOs

Read the Gruntwork contribution guidelines.

• [ ] Update the docs.
• [ ] Run the relevant tests successfully, including pre-commit checks.
• [ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• [ ] Include release notes. If this PR is backward incompatible, include a migration guide.
• [ ] Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)

Added / Removed / Updated [X].

Migration Guide

[denis256]

Looks like go mod tidy wasn't executed:

$ git status
On branch 23-timing-out-nuke-through-cli
Your branch is up-to-date with 'origin/23-timing-out-nuke-through-cli'.

nothing to commit, working tree clean
$ go mod tidy
$ git status
On branch 23-timing-out-nuke-through-cli
Your branch is up-to-date with 'origin/23-timing-out-nuke-through-cli'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   go.mod

no changes added to commit (use "git add" and/or "git commit -a")