imported and selected RIB outputs should not fall under BGP #525
Description
The rib_in and loc_rib RIB tables are used for more than just BGP. The API to dump these should not fall under BGP, since they are not BGP specific.
This is especially annoying in the case of a strictly static routing deployment, as you cannot dump either RIB table without supplying the ASN of a configured BGP router. So you'd have to create a dummy router + supply its ASN to the imported/selected query in order to view the RIB state of static routes.
This should live under a protocol-agnostic API endpoint which doesn't require an ASN as part of the query... and that change should also be propagated into the Nexus API as well.