Suggested by: @adschellevis

Log widget has a problem with config section unhide.

This finally concludes work on #880, left on -devel for a while
longer to double-check with the requesters.

(dashboard, widget api) fix https://github.com/opnsense/core/commit/82fd7db543ca69ca04dcfc3089496748e77f1a6d#commitcomment-17392735

translation and some style

This makes a lot more sense, just embed the schedule into the label.

This is the default for pf(4), we don't need a kernel patch to
override this.

o Gets rid of cron save/flush in the filter reload path.
o Gets rid of cron job injection into config.
o Move configure_cron() to the rules edit where it can be
  flipped in case of schedule changes.

To be totally frank, a 15 minute hook to deploy a time
based system is hardly accurate.  But what worries me more
is that we still have this patch in the kernel, totally
unsure of what it actually does when we have a schedule-based
reload on top anyway:

https://github.com/opnsense/src/commit/0a19f813177d18e569a457eff50a07c2e42abe04

Even though we take a hit for running through the filter rules
array again, it's the first step for sidestepping the need to
use the config to inject our cron job and flush the rules in
mid-reload...

o Synchronise the calls as there should be no drawback running
  in the background for a table flush.
o Locallise the after-filter hook to the two functions using it.
o Restrict the functionality to flush tables only.
o Remove some dead code along the way.

translation and coding style status_interfaces.php