GeezerVison

Closes #172

Summary

The password of the connect string could end up on screen in two ways:

1. Args debug line. At startup the CLI logs its command line arguments at debug level, connect string included:

   DEBUG org.utplsql.cli.Cli -- Args: run, app/Sup3rSecretPw@//localhost:1521/FREEPDB1
   

2. Passwords containing @. The connect-string parser ended an unquoted password at the first @. For app/p@ss@host, the password was taken as p and the connect string as ss@host. The connection failed, and part of the password appeared in the connection lines and in the driver's error message, printed on every run:

   jdbc:oracle:thin:****/****@ss@//localhost:1521/FREEPDB1: ORA-12261: ... connection string ss@//localhost:1521/FREEPDB1
   

Behaviour change

Passwords containing @ no longer have to be quoted, thought it's a good ide to keep it that way. Connect strings can not contain @ because everything up to the last @ is taken as the password.
This is fine as connect strings (EZConnect, TNS aliases, descriptors) don't normally contain @.