[partition] Remove unused locals

- Unused since commit 0d284759

[rawfs] Fix crash if bogus is unset

- Uses global storage to steer the jobs that are created, in case
  the slideshow needs to be tweaked by percentages or whatever.
- While here, add some code docs and apply coding style.

- In the test application, there is only one viewstep, so it is
  already activated; avoid double-activation.

- When loading QML V2, both loadQmlV2Complete() and changeSlideShowState()
  lock the same mutex, introduced in e7f4479d.
- Explicitly unlock when loading is done and we need to change the state
  immediately.

- This is needed for addModule() so the module manager knows there
  is a module by the name x@x.
- Tell the ExecutionViewStep to run jobs from x@x.

- When a viewmodule is loaded, register it with the module manager
  (especially relevant for the slideshow module).

- For testing purposes, it's useful to load a module externally
  and then register it to the ModuleManager (this hands off ownership).
- Refactor overall module loading to use the exposed single-module method.

- QML files need to be searched in specific places; this was initialized
  by Calamares, but not for the text application. Move initialization
  into the library.

- Use "Qml" in camel-cased names

- fixes:
	12:44:25 [6]: Python Error:
	 <class 'TypeError'>
	 'builtin_function_or_method' object is not subscriptable
	 File "/usr/lib/calamares/modules/rawfs/main.py", line 188, in run
	    item.copy(filesystems.index(item), len(filesystems))

	  File "/usr/lib/calamares/modules/rawfs/main.py", line 99, in copy
	    if libcalamares.job.configuration["bogus"]:

- If the slideshow fails to load entirely, say so

- The -s will run the slideshow with a bogus job-queue, allowing easier
  testing of the slideshow. This is more convenient than having a Calamares
  with an empty show and a bogus exec section.
- The -s option for running the slideshow / execution phase of
  Calamares needs to create a bogus Module for the ExecutionViewStep.

- Previously, unless setDefaultFontSize() was called explicitly,
  the default size would be 0, leading to unexpected and weird
  displays (and a warning on stderr).
- If setDefaultFontSize() is not called, get a sensible size instead
  (like defaultFontHeight() was already trying to do).

- The Q_FUNC_INFO was integrated into regular logging with commit
  5248a37e

- When loading *view* modules, we always need a QApplication for GUI
  bits, because the widget for a module is created is very early.
- If it's a view module, replace the application object with one
  that supports GUIs; without the --ui flag, though, it will just
  run the jobs.

- Update includes
- Use exposed API instead of accessing internals of the button

- Don't expose internals
- Drop unnecessary virtual
- Offer new API to do the things, for which internals were exposed

- Apply coding style
- Place the widget classes in namespace Calamares
- Export symbols for widgets

- QElapsedTimer has existed since Qt 4.7

QVariant::fromValue doesn't have *since* documentation, so I expect it to be 5.6-and-later.

make sure the listviews fit in the default window size without overlapping
the language bar