- validate nets and respective drivers like everything else
 - load the netlist earlier (in the user scripts) to make it available while
   loading settings
 - add a FIJI::Netlist parameter to respective FIJI::Settings's functions
 - add a new type 'driver' for FIU elements to distinguish its string
   representation from nets'
 - add new net validation function to FIJI::Netlist
 - use this to make net and FIU validation more generic to simplify FIJISettingsViewer
 - refine and correct handling of the tool phases
 - distinguish fatal errors, missing fields and less important anomalies when
   validating settings depending on the phase etc
 - notify user about validation problems in more detailed messages and tooltips
 - refine FIJI::VHDL to not load settings all the time and receive parameters
   directly instead of via hashes
 - use a global constant ONLY_LOAD in fiji_setup instead of a local variable
 - add a 'show_warning' function to ease opening warning dialogs
 - various other usability/GUI-related improvements
 - allow the deletion of nets

Otherwise, arguments to long options given with '=' are
not globbed.

Adress issue vecs/fiji#62

Also, do not repeat warnings as errors in GUIs and during instrumentation.

Due to the weird level mechanism of Log4Perl the we cannot (easily)
set the verbosity directly but only increase it. Rename functions and
variables to reflect this better and use the new function correctly.

Since the appender is defined in logger.conf and thus loaded by all
applications we need to remove it at load time from all applications
but the CLI EE tool.

I.e. fix the chaos that has been growing for a while and the bugs
introduced in the patch
"fiji_ee_gui: allow to abort test runs even during long transfers"

 - make all of them a function
 - use the same parameter and return scheme for said function
 - unify indentation, wording and parameter names
 - document verbosity parameter

Use this to set the available UART ports and default timer values.
The latter gets rid of FIJI::DEFAULT_TIMER_VALUE by replacing it with
FIJI::Settings::default_timer_value().

However, it requires some non-trivial changes, namely the refactoring
of FIJI::Tests. While at it, we got almost rid of the 'ext' field in
Tests. It is lessened to 'TESTPATMAP' containing info to verify tests.

The refactoring also allows for unification of opening of tests files
in the EE GUI. To that end this patch adds _read_tests_file() that
handles creation of the Tests instance and handle user interaction if
need be.

 - add a new pattern to the logger.conf file (and a fallback
   one hardcoded to FIJITestsViewer)
 - parse the config file within FIJITestsViewer and change the layout
   pattern of the QueueAppender accordingly
 - make sure the download worker uses the same logger configuration
   as the main thread by re-applying the same changes in the worker thread
 - also, add indentation to ordinary multi-line log messages

They are generated by DialogBoxUL automatically.

 - Change FIJIModalDialog to handle markup text with URLs.
 - Add a unified about text in a file.
 - Create a central show_about() and use that in Setup and EE.

TODO: docs/

Reuse code of show_documenation to create a generic
cross-platform open function.
Also, get rid of the extra help button in FIJI Setup and FIJI Download GUI.

This also makes delete_mw superfluous in FIJISettingsViewer and FIJITestsViewer.
'mw' always was useless because there exists a Mainwindow() in all widgets.

They are not useful in git. If need be they could be implemented by a
fudge/clean filter with git attributes.

We can check if the main window still exists with Exists() instead.
This may also have fixed the problem with joining all threads...

No other changes were made.

Put download_worker code into eval and report its demise to the GUI
via $queue_to_gui.
This allows us to abort safely on fatal errors like missing packages (if
nothing else interferes... I am looking at you Tk!)
To that end install an afterIdle event handler that checks for said
message, displays an error dialog and exits the GUI when the user has
acknowledged the problem.