Restore resaveAllEppResourcesPipeline as a cloud task

[ptkach]

This change is 

[weiminyu]

Let's hold off with this. I have doubt about that pipeline. Specifically:

nomulus/core/src/main/java/google/registry/beam/resave/ResaveAllEppResourcesPipeline.java

Line 196 in 71a8579

options.setIsolationOverride(TransactionIsolationLevel.TRANSACTION_REPEATABLE_READ);

Reviewable status: 0 of 2 files reviewed, all discussions resolved (waiting on @jianglai)

[jianglai]

I think it should be fine? Each resource is projected into the future independently so there should be no possibility of serialization anomalies.

Reviewable status: 0 of 2 files reviewed, all discussions resolved

[weiminyu]

I was thinking about concurrent updates. Since we always update the timestamp, it should be okay.

Reviewable status: 0 of 2 files reviewed, all discussions resolved

[weiminyu]

Reviewable status: 0 of 2 files reviewed, all discussions resolved

[jianglai]

FYI, if you are concerned about the blast radius of this job, consider enabling it in sandbox first and verify the results before enabling it on production.

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @ptkach)