When applying a custom routing table different from the main one, nmstate takes the first route with destination 0.0.0.0 even if it does not belong to the main routing table

I didn't hit this in the previous deployment, so I think it depends on the order with nmstate returns the routes. So, not always

1.

File a route with a different table id, with a default gateway, like                                                                                                          
  - destination: 0.0.0.0/0                                     
    next-hop-interface: eth0                                  
    next-hop-address: 169.254.169.4                            
    table-id: 56                                                                                                              

2. 
 3.

if we hit the bug, knmstate will try to ping 169.254.169.4

knmstate should ping the actual default gateway to understand if the node is healthy