Pass the entire page data to the ModulePage

As module wizards might require some configuration values aggregated by
the main application wizard we pass the entire page data to each wizard as
if the data were aggregated by a module wizard itself.

refs #7163
Do not use getForm() but getCurrentPage() to avoid page creation

refs #7163
Pass the wizard title to the summary page to be able to reuse the page

Module wizards can now use the SummaryPage as well if they want to.

refs #7163
Revert "Create sub directories with the CLI's setup command as well"

This reverts commit 9589919ae84e41cb505078ec641b4715dff74bff.
Create configuration sub directories as part of the setup wizard

refs #7163
Fix that the ModulePage cant find modules when being asked for

refs #7163
Fix the ModulePage's request handling

This caused a module's summary page not being able to render the
summary as /<ModuleSetup>/->setupPage() is never been called
after a wizard is completed.

refs #7163
Move MakeDirStep to Icinga\Web\Setup

refs #7163
Drop Icinga\Application\Installation and introduce Icinga\Installation

refs #7163
Allow install steps to return no summary

refs #7163
Add EnableModuleStep

refs #7163
Do not show a summary for the MakeDirStep

The user does not configure anything this step will process so there is no
need to show the user a summary about something he can't control.

refs #7163
Fix grammar..
Let wizard buttons have some bottom margin

Makes them more notable in case they'll get
pushed to the very bottom of the page.

refs #7163
Improve feedback when creating the configuration directory using the CLI

The user gets now a success message as well as not a failure message in case the directory already exists.

refs #7163
Fix WelcomePage

There were some grammar- and layout-errors
as well as information missing :(
Fix that the ModulePage does not provide a wizard's requirement info

refs #7163
Add monitoring module wizard

refs #7163
Use a hardcoded path where to look for modules

refs #7163
Do not throw an exception in DbTool due to an implementation detail

Throwing exceptions due to failing logic which is purely an implementation
detail must not affect the calling code in any way.

refs #7163