Add a mechanism to route vendor methods

Each vendor class had to implement a custom method
to invoke their own vendor functionalities, the commit
e129faef1762b8335b226298554ed83204c2696a added a decorator @passthru()
to decorate those vendor methods and guarantee that the errors and
exceptions are being handled accordingly. This patch is extending that
decorator to add some metadata to each vendor method and from that be
able to generically build a way to invoke those without requiring vendor
drivers to implement a custom method for that.

The vendor_passthru() and driver_vendor_passthru() methods were removed
from the VendorInterface base class. Now vendors that wants to implement
a vendor method should now only care about implementing the method itself
and decorating them with the @passthru() or @driver_passthru decorator.

This patch also adds a backward compatibility layer for existing drivers
out of the tree that may be using the old [driver_]vendor_passthru()
methods. If the vendor class contains those methods we are going to
call them just like before, otherwise we are going to use the new
mechanism. All drivers in tree have been ported to the new mechanism.

Implements: blueprint extended-vendor-passthru
Partial-Bug: #1382457
Change-Id: I7770ccd9668d9c03e02f769aff7c54b33734a770
Fix documentation on Standard driver interfaces

This fixes the documentation by removing 'rescue' (since we don't
yet have any rescue interface) and adding 'management' interface
to the list of Standard driver interfaces.

Change-Id: I34110fecbcff9c75d0f769eb3694eb509ec39e27