handle other route types

[grizz]

Currently only does BGP, should support everything

[mkomon]

Other route sources are vaguely supported but protocols other than BGP (well, that will be mostly OSPF) could get some additional attributes parsed, such as metric, metric type, advertising router, route type (inter/intra area, sumary) etc. Below is what pybird parses for routes from different protocols:

# BGP
{'origin': 'IGP', 'as_path': '1234 5678', 'next_hop': '198.51.100.1', 'local_pref': '100', 'community': '1299:20000 30962:1299', 'prefix': '192.0.2.0/24', 'peer': '198.51.100.1', 'interface': None, 'source': 'ff4', 'time': '19:56:31.328'}

# OSPF
{'prefix': '198.51.100.0/24', 'peer': None, 'interface': None, 'source': 'ospf1', 'time': '12:40:33.797'}

In addition, pybird could provide information about routing neighbors. It is a design decision made in BIRD that only one peer is allowed per BGP instance which creates this "protocol instance = peer" mapping. Other routing protocols in BIRD (OSPF RIP) can have multiple dynamic neighbors per protocol which would have to be handled differently in pybird.