NLSR

Currently, when the LSDB publishes a routing update, the LSDB constructs the LSA update prefix. The same code appears in 4 different places in lsdb.cpp.

ndn::Name lsaPrefix = m_nlsr.getConfParameter().getLsaPrefix();
lsaPrefix.append(m_nlsr.getConfParameter().getSiteName());
lsaPrefix.append(m_nlsr.getConfParameter().getRouterName());
m_nlsr.getSyncLogicHandler().publishRoutingUpdate(m_nlsr.getSequencingManager(), lsaPrefix);

Also, the LSDB passes a SequencingManager obtained from the Nlsr instance each time it calls publishRoutingUpdate.

Instead, SyncLogicHandler should construct and maintain the LSA update prefix and have a reference to the Nlsr's SequenceManager.

SyncLogicHandler::publishRoutingUpdate can be refactored to take no parameters and the LSDB can simply call:

m_nlsr.getSyncLogicHandler().publishRoutingUpdate();