Prefer passing display opts to watch, not request

This patch is backwards compatible.

Console warnings are issued when display options (siteName, siteLogo,
backgroundColor) are passed to .request().

Rationale:

In the future, we hope that browsers will have native support for the BrowserID
protocol. It would be nice if those browsers could display properly themed "sign
into this site" buttons in the native browser UI.

If display options are passed to .request(), they're not known until the user
clicks "sign in" on the site itself. On the other hand, if they're passed to
.watch(), they're known by the browser as soon as the site loads, and can be
used without requiring direct user interaction with the page.

Related to #4134
We don't show warnings for folks using visual customization with `.get`, since there would be no way for them to solve it. "Pass those to .watch? But I don't have a .watch!"

Another way to think about it is that .get is deprecated, but passing those options are not separately deprecated.

Once Goldilocks is stable, we'll add full-on deprecation warnings to Get and Observer, and publish migration guides to Goldilocks