OSPF Assertion Behaviour

[rickdonato]

Describe the bug There are situations around OSPF assertions that could be updated. For example:

1. There is no OSPF data due to the poller being unable to collect the data. This negates an assertion failure being raised.
2. OSPF is not configured on the device. This behaviour needs to be handled in addition to the first point.

To Reproduce N/A

Attach N/A

Expected behaviour

1. If one side has OSPF enabled. then the neighbour interface (i.e the side that has no data) is added to the table and marked as (assertion failure missing data)
2. Only in cases where no OSPF is seen (in terms of config) on both sides would the device's interfaces not be added to the OSPF table. Otherwise, the same logic would apply as point 1.