Set updated status when sanitizing secrets

[szh]

Desired Outcome

When a secret retrieval operation fails with a 403 or 404 error, we remove the stored secrets. See #447, #449
This PR changes the behavior of the status reporter (added in #450) to report a successful update when this sanitization occurs, even though an error is also returned. This way the consuming application will know that the secrets have changed.

TODO: Do we need integration tests to ensure the sentinel files are being created?

Connected Issue/Story

N/A

Changelog

• The CHANGELOG has been updated, or
• This PR does not include user-facing changes and doesn't require a
  CHANGELOG update

Test coverage

• This PR includes new unit and integration tests to go with the code
  changes, or
• The changes in this PR do not require tests

Documentation

• Docs (e.g. READMEs) were updated in this PR
• A follow-up issue to update official docs has been filed here: insert issue ID
• This PR does not require updating any documentation

Behavior

• This PR changes product behavior and has been reviewed by a PO, or
• These changes are part of a larger initiative that will be reviewed later, or
• No behavior was changed with this PR

Security

• Security architect has reviewed the changes in this PR,
• These changes are part of a larger initiative with a separate security review, or
• There are no security aspects to these changes

[codeclimate]

Code Climate has analyzed commit 42977aa and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 89.2% (0.2% change).

View more on Code Climate.

[rpothier]

LGTM!