frrender: T9442: reload FRR when the rendered configuration was not applied

A failed reload only dropped the in-memory cache. The record of the
configuration FRR runs still held the previous one, so the DHCP render
helper skipped a return to it while FRR kept a part of the failed
configuration. After a rejected reload test, the rendered file also kept
the rejected configuration.

Change detection now also requires the rendered file to match the
applied one, and a failed reload removes that record. The next commit
then renders and reloads FRR again, even when it returns to the
previous configuration.

A smoketest stops FRR during a commit and verifies that committing again
brings the configuration into FRR.

0 files changed, 0 insertions, 0 deletions