Implement rollback API for providers

[judahrand]

What this PR does / why we need it:
Addresses the issue mentioned. This is very much a first pass solution so keen for any and all feedback.

Which issue(s) this PR fixes:

Fixes #2116

Does this PR introduce a user-facing change?:

None

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: judahrand
To complete the pull request process, please assign achals after the PR has been reviewed.
You can assign the PR to them by writing /assign @achals in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[feast-ci-bot]

Hi @judahrand. Thanks for your PR.

I'm waiting for a feast-dev 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/test-infra repository.

[judahrand]

The AWS failures make it a bit tricky to tell that this is working as intended. I'm not sure how to proceed on that front.

[felixwang9817]

@judahrand thanks for this PR! we believe we've fixed most of the issues with AWS integration tests (we increased the size of our Redshift cluster for tests and found a bug here that kept leaking Dynamo tables), so we're hoping the tests are fine going forward (we still expect occasional leakages until this issue has been resolved, but they should be very manageable)

as for the rollback API, we're still considering whether it should be supported, but for now since tests should be fine, let's put a hold on this PR!