fix 2 problems plus add workaround for #13760

[philwalk]

replaces #14241

These changes fix 2 problems, and add a workaround for #13760.

• script exceptions are discarded by MainGenericRunner, when running from a compiled jar.
• when the -save option is not specified at runtime, execution should not be from a previously compiled jar

The -save behavior matches the expectation in scala2.

This PR displays all exceptions on the Console when running from a jar file.

This PR executes from the jar only if the -save option is specified at runtime. Problem scripts (i.e., with references to java.sql.Date) can now selectively disable the -save option.

The -save option change provides a workaround for the ClassNotFound: java.sql.Date problem, which affects jdk 9+.

`java.lang.ClassNotFoundException: java.sql.Date`

A new command line option -nosave is provided, for undoing a -save option on the command line (e.g., inSCALA_OPTS) This provides a way for individual scripts to override the -save option.

Adding -save to SCALA_OPTS will typically reduce script startup time by a couple of seconds. This PR provides per-script granularity for overriding the '-save' option. Scripts that would otherwise throw an exception when running from a compiled jar may specify -nosave in the hashbang line. This avoids having to remove the -save option from SCALA_OPTS.

The -nosave option can be added to the hashbang line, as in these two example hashbang lines:

The first version requires /usr/bin/env version 8.30 or later:

#!/usr/bin/env -S scala -nosave

This version uses the path to the scala wrapper:

#!/opt/scala3/bin/scala -nosave

[BarkingBad]

LGTM