floating pages such as this one into a 'Lobby' category?  Discuss.  :)

* Update the crash report version information.

* Tweak the form layout and remove HTML errors.

* Show appropriate message instead instead of redirect.

* Rework POST actions for style and sanity.

* Refactor crash report link into a function so it could be called
  from any page if desired.

* Do not show a crash report when there is none.

While there, move errors to where they should be checked.

(Hint: as early as possible.)

That's what you get for using "@" muting informative errors.

Use internal classes to restore a backup, to prevent overwrite by our singleton object

The GUI upgrade still has serious problems coping with the
fact that it is being updated.  In the latest upgrade the
move of set_language() causes an error so we just avoid it
and do the work again when we can.

last bits and pieces for https://github.com/opnsense/core/issues/117 although rc.filter_synchronize really needs a rewrite at a later moment.