Add final sweeper error to logs

[gdavison]

If the sweeper framework returns an error, such as a missing sweeper dependency, the error is not displayed to the user.

...
2022/06/14 13:06:18 [DEBUG] Sweeper (aws_redshift_scheduled_action) already ran in region (us-west-2)
FAIL	github.com/hashicorp/terraform-provider-aws/internal/sweep	58.064s
FAIL
make: *** [sweep] Error 1

Now logs the error

...
2022/06/14 14:21:45 [DEBUG] Sweeper (aws_appconfig_configuration_profile) already ran in region (us-west-2)
2022/06/14 14:21:45 [ERROR] Sweeper (aws_docdb_global_cluster) has dependency (aws_docdb_cluster), but that sweeper was not found
FAIL	github.com/hashicorp/terraform-provider-aws/internal/sweep	60.860s
FAIL
make: *** [sweep] Error 1

[bflad]

This makes sense to me if it is relating to when the "allow failures" flag is also set. Could you add a changelog entry as well? e.g. .changelog/983.txt and

```release-note:bug
helper/resource: Ensured errors are always logged when `-sweep-allow-failures` flag is set
```

[gdavison]

No, --sweep-allow-failures isn't set and it's stopping at the first error, which is that the dependency doesn't exist. runSweeperWithRegion fails with an error, but gives no reason why

[bflad]

Fair enough -- changelog comment still applies, I guess more generically "helper/resource: Ensured sweeper errors are always logged"

[bflad]

Looks good to me 🚀

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.