Enable documentation for chrome.printerProvider API

Enable documentation for chrome.printerProvider API

Also, a small update to the documentation in idl file.

BUG=408772
TEST=Checked out server2/preview.py

Committed: https://crrev.com/f899366965bbfab8be9d19eb0eaff56a2c50acb3
Cr-Commit-Position: refs/heads/master@{#317133}

[tbarzic, 2015-02-19 18:43:31]

tbarzic@chromium.org changed reviewers:
+ kalman@chromium.org, vitalybuka@chromium.org

[tbarzic, 2015-02-19 18:43:32]

kalman: https://chrome-apps-doc.appspot.com/_patch/933353002/apps/api_index
lists printerProvider as a stable API. Any idea what could be wrong there? (the
API did not have "channel" property set in _permission_features before 42, maybe
that could be related)

[Vitaly Buka (NO REVIEWS), 2015-02-19 19:03:49]

lgtm

[not at google - send to devlin, 2015-02-19 19:48:12]

lgtm. The channel thing could be either a lack of channel in the features file,
or simply that channels don't work with patched-in files since there's no
version associated with it really.

Just see how it looks when it's submitted.

[tbarzic, 2015-02-19 19:57:04]

The CQ bit was checked by tbarzic@chromium.org

[commit-bot: I haz the power, 2015-02-19 19:58:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/933353002/60001

[commit-bot: I haz the power, 2015-02-19 21:07:03]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-02-19 21:07:23]

Patchset 4 (id:??) landed as
https://crrev.com/f899366965bbfab8be9d19eb0eaff56a2c50acb3
Cr-Commit-Position: refs/heads/master@{#317133}

[tbarzic, 2015-02-20 20:45:28]

On 2015/02/19 21:07:23, I haz the power (commit-bot) wrote:
> Patchset 4 (id:??) landed as
> https://crrev.com/f899366965bbfab8be9d19eb0eaff56a2c50acb3
> Cr-Commit-Position: refs/heads/master@{#317133}

hm, looks like it is listed as stable api :/
https://developer.chrome.com/apps/api_index

[not at google - send to devlin, 2015-02-20 20:49:51]

Alright. Perhaps augment the description with "Since Chrome 42" for now, and I
can look into why the wrong availability is being generated.