Minimal shell: honor full chain of hooks, on either minimal entry point

[glima]

We have 2 points in which LISA might decide to go with a minimal shell profile:

1. When first contacting a node, issuing a 'cmd' command, checking if
   'Windows' is present in the output or not (rule out Windows shell
   type). A negative case will incur in either the POSIX shell type,
   if 'Unknown syntax' is not thrown as output, or an early
   decision for the 'minimal' shell type is taken and the shell object is
   set to follow that config from there on.

2. When running the actual first lisa suite SSH command on the same
   node. It turns out we've seen cases where 'Unknown syntax' is not
   output at early node initialization (1), for some reason. Well, the
   exception path of actual command execution will check internal node
   state, that tracks if a minimal profile has been tested before or
   not. If not used yet and under a command execution exception, set the
   node to minimal type and try again was the logic.

It turns out the 'minification' of the node config was only done
partially, in (2). We missed the full logic of overriding its final
SSH command tokenizer.

Another missed detail is that the final tokenizer logic at the minimal
shell case was too greedy in trying to remove stray quotes. Let's keep
injecting quotes on tokens with spaces on them. That will not hurt any
legit commands from any minimal context.

[squirrelsc]

@lubaihua33 @LiliDeng LGTM, please verify it.

[LiliDeng]

@glima please fix CI check error.

nox > flake8 
./lisa/util/shell.py:215:1: BLK100 Black would make changes.
./lisa/util/shell.py:215:1: E302 expected 2 blank lines, found 1
./lisa/util/shell.py:320:5: E303 too many blank lines (2)

[glima]

@squirrelsc do I get it in?

[LiliDeng]

@glima please fix the CI check error, thanks.

./lisa/util/shell.py:49:19: BLK100 Black would make changes.