Add cli option to disable the default global zones

[RincewindsHat]

When setting up Icinga 2 agents, in most cases, the default global zones are not needed, but have to be removed manually or automatically whith tools outside of Icinga 2 from the configuration.

This seems like unnecessary work, since the node setup command does everything else.

This commit introduces a new option for the node setup command ("--no-default-global-zones") to exclude the default global zones.

fixes #10023

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Lorenz Kästle.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[RincewindsHat]

@Al2Klimov ok for me

[Al2Klimov]

Please add that new switch to the node setup documentation.

[RincewindsHat]

I did add documentation in the table for the node setup command.
The changes look a bit messy, since I had to change the alignment in the whole table.

[julianbrost]

Change is fine for me now.

I'll try to push a rebased version (git rebase $(git merge-base origin/master HEAD), no changes, no conflicts) right afterwards to get rid of a merge commit within the PR. (If that doesn't introduce new changes, that should leave the approval intact, that's why I'm doing it that way around.)