[cli] fix publish:rollback

[quinlanj]

why

fixes #596

how

• change implementation to do a publish:set of the second most recent thing in history for a given sdkVersion, platform and channel instead of actually deleting anything in the history
• add confirmation with the publication that clients will receive as a result of the rollback
• move shared methods into PublishUtils

tests

• repro on a client
• publish rollback unit tests pass

[codecov-io]

Codecov Report

Merging #1707 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1707   +/-   ##
=======================================
  Coverage   60.12%   60.12%           
=======================================
  Files          89       89           
  Lines        2573     2573           
  Branches      667      674    +7     
=======================================
  Hits         1547     1547           
+ Misses       1001      994    -7     
- Partials       25       32    +7     

Impacted Files	Coverage Δ
packages/pwa/src/Manifest.ts	37.25% <0.00%> (ø)
packages/config/src/Config.ts	66.66% <0.00%> (ø)
packages/config/src/android/Manifest.ts	69.79% <0.00%> (ø)
...ackages/webpack-config/src/addons/withDevServer.ts	33.33% <0.00%> (ø)
...es/webpack-config/src/loaders/createBabelLoader.ts	46.66% <0.00%> (ø)
...webpack-config/src/plugins/FaviconWebpackPlugin.ts	4.76% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 12f8517...d648b56. Read the comment docs.

[brentvatne]

could you add some unit tests here? ideally all new code being added to expo-cli should improve test coverage

[quinlanj]

@brentvatne here they are! #1724

[fson]

Since --release-channel and --sdk-version are required arguments, if people omit them, we could look up what their most recently published release was and show more contextual instructions how to roll that back:

> expo publish:rollback
--release-channel and --sdk-version arguments are required.
For example, to roll back the release [a1f0c0] on release channel [default] (published 10m ago),
run: expo publish:rollback --release-channel default --sdk-version 37.0.0