Add ViewModeSwitcher control

[BastianLedererIcinga]

resolve #340

A ViewModeSwitcher class similar to the one in icingadb-web is added. It was reworked so that adding and removing view modes can be done without declaring a subclass.
To allow this the ViewMode class is added, which contains name, icon, titles for active/inactive state and the default page size.

The Controls trait is added with a createViewModeSwitcher() function.
It registers a listener to ViewModeSwitcher::ON_REQUEST, which populates the ViewModeSwitcher with the view mode from the url and emits ON_VIEW_MODE_SET.
If the view mode is changed, a ViewModeSwitcher::ON_SUBMIT listener emits ON_VIEW_MODE_CHANGE with the ViewModeSwitcher, its previous view mode and a $redirectUrl that listeners may modify.

The handleControls() function suggested in #340 is implemented, which calls handleRequest() for all controls passed to trackControl() , in case of the ViewModeSwitcher this is done by the factory method.

The CompatController registers listeners on the trait's events in the createLimitControl() and createPaginationControl() factories, to adjust the default limit, page size to teh current view mode, and correct the current page when the view mode is changed.

SearchControls::createSearchBar() is adjusted to shift the view mode param before building its filter, because the Controls trait does not have access to the UrlParams.

[sukhwinder33445]

The view mode switcher is no longer aligned to the right as it was before:
Before:

Now:

Please fix the alignment and style.

[sukhwinder33445]

Apart from the changes I’ve pointed out, the code looks fine to me.

[sukhwinder33445]

@nilmerg please have a look.

[nilmerg]

I'm not really convinced that this follows what I proposed in the issue. The view mode dependent limit change is not automatically done anymore, and the dynamic correction of the current page is missing. Custom rules, so to say, are also not even considered.

And where's:

So the new implementation should allow to add new modes as well as to remove default modes.

It also misses basic accessibility support, as the id protection has no fallback. Since it is now a library part I consider this a must, as unique ID's are not a requirement of Icinga Web, only the part that it must be based on the container id. ipl-html also provides a fallback in case of the new decorator implementation for this very reason: A sane default.

So this is far from finished, I'm afraid.

[nilmerg]

Looks fine now, thank you. Though, I will first check any dependent implementation before merging it.

[nilmerg]

🎉