Restore legacy publicize ui

[gravityrail]

WIP experiment.

cc @jeffgolenski

[matticbot]

Caution: This PR has changes that must be merged to WordPress.com
Hello gravityrail! These changes need to be synced to WordPress.com - If you 're an a11n, please commandeer, review, and approve D31639-code before merging this PR. Thank you!

[jetpackbot]

	Warnings
⚠️	"Testing instructions" are missing for this PR. Please add some
⚠️	"Proposed changelog entry" is missing for this PR. Please include any meaningful changes

This is an automated check which relies on PULL_REQUEST_TEMPLATE. We encourage you to follow that template as it helps Jetpack maintainers do their job. If you think 'Testing instructions' or 'Proposed changelog entry' are not needed for your PR - please explain why you think so. Thanks for cooperation 🤖

Generated by 🚫 dangerJS against 90a88e7

[lezama]

@gravityrail We are seeing the same tests failing in #13230, it seems something deep in core master.

[jeffgolenski]

@gravityrail I'll give this a test once the checks pass and it shows up in the beta app! FYI, I'm AFK until wednesday though.

[gravityrail]

@jeffgolenski tests fixed, let me know when you've taken a look. I'm interested to know if we can give this old UI a coat of paint so it fits in with modern Jetpack

[gravityrail]

cc @oskosk who was also pinged on #12937

Related: #12929

[jeffgolenski]

The functionality of the connections seems to work just fine (tested with linkedin). But we'll need to have a larger dicussion around overall UX / UI to bring this up to speed in 2019!

[stale]

This PR has been marked as stale. This happened because:

• It has been inactive in the past 3 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this PR has clear testing instructions, is it up to date with master, and it is still valid. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.