App should check for running instances when app binary is directly used as CLI interface with wrong arguments and give a notification about multiple running instances

[waydabber]

When there are uninterpreted arguments provided to the app binary, the app will respond with Some uninterpreted or system arguments are present - proceeding with app launch. - however this behavior might not be the desired one when the app is already running.

This results in this:

[waydabber]

The app will now respond with this message and refrain from launching an additional instance when an app instance is detected to be running already. This probably aligns better with the intention of the user.

Some uninterpreted or system arguments are present - would proceed with app launch, but an instance is already running so exiting instead. To launch an additional instance deliberately, please launch the app binary with no arguments or add the 'skipArgumentsCheck' argument to skip this check.

[waydabber]

Decided not to fix this instead as the solution would not work well in a multi-user environment (there are legitimate reasons to have multiple instances running) and identifying the user ID of processes is not straightforward enough to reliably build a solution based on that (or it would be overkill to fix this issue).

The app will still show a warning about multiple instances but not prevent launching these, for example:

Some uninterpreted or system arguments are present - proceeding with app launch. Please note that the app already had 2 running instances and now an additional instance was started. This might not be what was intended!