This is tracking the upstream effort needed to deliver the feature request described below.

Currently the "advertised_route_sync" engine node in northd takes care of synchronizing static and dynamic routes to SB. Both of them have separate node that takes care of actually aggregating the routes that should be advertised. There is one exception and that is if user sellected connected-as-host, those routes are aggregated during the en_advertised_route_sync_run(). That makes it hard to manage inputs of the sync. The goal is to separate the connected as host to another node, possibly into existing one or completely new one. This should make it easier to add I-P support for advertised routes.

Note: The QE testing in this case should be sanity only, this change should be transparent to the user.