Part 1 of 2 for "Log-on not successful" bug when using ProtonMail.

The curl login check defaults to `imaps` when `protocol` isn't set.
Because ProtonMail isn't using any TLS, we have to use the `imap`
protocol.
The `protocol` variable was never set, so now we set it when the
ProtonMail flag (-p) is set.

Bug mentioned in:
Fixes:
- https://github.com/LukeSmithxyz/mutt-wizard/issues/608
- https://github.com/LukeSmithxyz/mutt-wizard/issues/622

cloe #367

rm mbsync requirement for online storage

the new script manually searches for environmental variables
so that it can work from a cronjob
and additionally searches for all Xorg displays on Linux
so that the display notification should appear correctly
no doubt there will be more bugs, but this is what the people want
and it's worth working out

The Mac version of paste requires "-" to read from STDIN. Without "-", the "mailboxes" line in ~/.config/accounts/<email address>.muttrc is empty upon adding a new mailbox via `mw -a <email address>`. The Linux version of paste works fine if "-" is added.

under the inbox is used for something else
closes #581

It was a bit confusing when it said "use `w -y user@example.com` to sync your mail"

Today's mutt-wizard does not support the XDG Base Directory specifications (https://wiki.archlinux.org/index.php/XDG_Base_Directory) because it says the user should be able to change the config, cache, data folders etc. using the environmental variables XDG_CONFIG_HOME, XDG_CACHE_HOME, and XDG_DATA_HOME, and instead hard codes the default paths ~/.config, ~/.cache, and ~/.local/share. My commit corrects this.

-E option is cross platform and interprets
pattern as regular expression always

Co-authored-by: Aisha Tammy <aisha@aisha.cc>

I believe this addresses issue #456 where if you add a protonmail account you get an error.  This is caused by prematurely returning from the case statement that queries whether you have a protonmail account or not.

Co-authored-by: rjl6789 <rlives6789@gmail.com>

I think a recent change tried to send output from crontab to dev/null to avoid messages appearing a) when setting the crontab, b) whenever mailsync is run.  However the redirection was for the string concatenation meaning a null string was piped to cron obliterating the crontab (thank goodness for backups). I have put the redirection in the correct location (similar to a few lines above when removing the mailsync line).  I have also redirected all output of the mailsync (both errors and normal messages) to dev null.

Co-authored-by: rjl6789 <rlives6789@gmail.com>

Let's make crontab a little quiet here, unless for those who set up mail for crontab error handling will be disturbed every few minutes.

* Simple Fixes

* Tweak wording

* Update openfile

* ShellChecked

* Little Fixes