Please document drush compatibility

Issue Summary

We noticed that drush automatically respects the settings of the update_advanced-module. I assume this works because drush uses the update-module for the updates, and update_advanced integrates with it?

So if I have set "views" to update "never" at http://example.com/admin/reports/updates/settings , "drush up views", it will show views as "Unable to check status " and respond "No code updates available." even if there are updates. Exactly what we need to exclude patched modules from being overwritten.

In any case, it works fantastic, but surprisingly, this feature is not documented anywhere (!), at least not in drush or update_advanced's issue queues (drush & update_advanced).

This combination has been very useful, we have been using it in our workflow for about a year now. It's the reason we even use update_advanced, apart from documentation.

Sorry for screaming for attention by setting this to "major", but I believe if this fact was properly documented (maybe even on the frontpage of the module), this module might have a lot more (happy) users.