refactor: Fix boolean traps in signatures

[pederhan]

This PR adds the Ruff rule FBT002, which detects positional boolean arguments in signatures that have a default value.

The affected function parameters are all changed to be keyword-only, so that we don't have hard-to-understand function invocations in the codebase wherein some positional bool decides the behavior of something, i.e.:

Authenticator.get_zabbix_url(True)

When it should be:

Authenticator.get_zabbix_url(prompt=True)

Adding this rule has highlighted that I am way too fond of this pattern, and I should be more mindful of how I write functions in the future. Does every function need some switch that enabled/disables some behavior? Looking at the codebase, probably not. These boolean toggles are rarely/never used.

FBT001 & FBT003

We cannot activate the FBT001 and FBT003 rules yet, since we use a lot of bool annotated positional args, as well as positional bool defaults for Typer options in commands. We need to migrate to the Annotated approach in order to use these without adding a bunch of # noqa comments all over the codebase (which is not worth it for essentially 0 gain).