(v3) some error messages thown by attachRowanDevClones.stone don't look like error messages and can lead people astray

[dalehenrich]

@LisaAlmarode got this output from the script and didn't realize that the message meant that an error had occurred:

The attach script (once corrected... archbase incomplete), produced one message that is probably not an error but I'd rather not see, complaining about components directory:
[2:22](https://gemtalksystems.slack.com/archives/C03SKU8HL5V/p1716326567822039)
lacomb:/lacomb4/users/lalmarod/jforpharo/gemstone/data> $GEMSTONE/rowan3/bin/attachRowanDevClones.stone --projectsHome=$ROWAN_PROJECTS_HOME --archBase=/lacomb4/users/lalmarod/jforpharo/gemstonecheckout/
Using ROWAN_PROJECTS_HOME = /lacomb4/users/lalmarod/jforpharo
Rowan version: 3.2.0
Using ARCHBASE = /lacomb4/users/lalmarod/jforpharo/gemstonecheckout
gemstoneBaseImage project attached and reloaded
No component directory ('/lacomb4/users/lalmarod/jforpharo/FileSystemGs/rowan/components') found for project 'FileSystemGs'

Should add a message something like "operation aborted; no commit performed"

[dalehenrich]

looks like with 3.7.2, the way errors are being printed in superdoit has changed as well ... for the worse ... I just had a case where an error occurred and no message was printed at all ...

This needs to be fixed and should probably be done in concert with internal bug 50877 ...