Currently, most of the rib(9) KPI does not use rnh pointers, using fibnum and family parameters to determine the rib pointer instead.
This works well except for the case when we initialize new rib pointers during fib growth.
In that case, there is no mapping between fib/family and the new rib, as an entirely new rib pointer array is populated.
Address this by delaying fib algo initialization till afters switching to the new pointer array and updating the number of fibs.
Set datapath pointer to the dummy function, so the potential callers won't crash the kernel in the brief moment when the rib exists, but no fib algo is attached.
This change allows to avoid duplicating existing functions with an altered signature.