Rollback increase timeout for deactivating failpoint

[henrybear327]

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

Because etcd-io/gofail#64 is merged, we can roll back the change.

Reference:

• Increase timeout for deactivating failpoint #17719

[k8s-ci-robot]

Hi @henrybear327. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[henrybear327]

@ahrtr when gofail 0.2.0 is released, I will update the gofail dependencies in another PR and rebase this one on top of it!

Currently, this PR serves as double-checking the CI is still working normally after the recent gofail final changes are merged before releasing the new tag!

Update: using the new gofail commit, the CI passes normally, and rolling back the change so far looks fine!

[henrybear327]

Pending PR etcd-io/gofail#69 to bump gofail to 0.2.0 (etcd-io/gofail#65 (comment))

[henrybear327]

/ok-to-test

[serathius]

Don't think we need to block in integration tests