This is really an error condition, so like the jsdocs say:
return undefined upon error

This how read(0) worked in sbbs, but not jsexec before that last commit,
so now just make readln and read work like that in both sbbs and jsexec.

Many global functions now throw an exception when null or undefined is passed
as a required parameter where null or undefined makes no sense.
e.g. "Argument #1 is an unexpected 'null' or 'undefined' value"
Example exception: is-a/has-a type functions will still return false when
passed null or undefined.

Changed global function return types:
- write() now always returns undefined
- printf() always returns a string, never undefined or garbage string
- prompt() returns null (not undefined) upon no input (as documented)

sbbs works more like jsexec:
- read(0) now returns an empty string instead of undefined
- readln(0) no longer waits for enter

jsexec works more like sbbs:
- add missing write_raw() global function, alias for write()

Include expected number of argment in "Insufficient Arguments" exception
message.

Update JSDOCS for some global methods:
- file_chmod returns boolean, not number
- flags_str requires a minimum of one argument

New tests to validate expected exceptions and return types based on usage.

Updated TS4S so we can build with -t while issue #777 is ongoing.

Ran `npm audit fix` to address a security issue in some dependency
of the build system. Perhaps this will silence the alert GitHub
sent to DM; I'm not sure what that was.

Don't use chdir(), just use js.exec_dir instead (e.g. for location of test.crt)

Use console instead of stdout when stdout isn't defined.

Log the file and line number of an an exception in a nested test when it
happens.

Fixes #794, esc exits. Other hotkeys reassigned per discussion
that happened I think on DOVE-Net.

Fixes #818, show/hide cursor on netmail.

Was overriding value, not appending.

It appears that setcap may cause $ORIGIN to stop working for some
unknown reason.

Not sure how I missed this one.

In this mode, SyncTERM won't will/do TELNET_BINARY_TX at the start
of a connection, leaving the mode up to the remote system. The main
purpose for this option is to work around a bug in older Synchronet
releases where early CTRL-C checking wouldn't work in binary mode.

Implements feature request 91.

Suitable for passing to console.gettemplate() when prompting for a birth date.

I'm using like this in my logon.js to correct corrupted newuser birth dates:
  while(user.age < 10) {
	console.putmsg(bbs.text(bbs.text.EnterYourBirthday));
	user.birthdate = console.gettemplate(system.birthdate_template);
  }

- date_format
- date_separator
- date_verbal
- birthdate_format

See JSDOCs for details

... make them more useful (e.g. when the result of script is a big string).

This will prevent the cursor from showing up when redrawing the
status bar, and implements feature request 79.

This isn't great, but it works (on FreeBSD)

It was at absolute max (an extra one and it would clip) which is
really a terrible thing to do to people wearing headphones.

I don't really need to do it this way, but the math for the different
wave forms depends heavily on integer wrapping (and WAVE_SHAPE_SINE_HARM
is just stupid).

Compile-time isn't the best time for configuration.

The first argument after the list was still being replaced.
Extended test to try the hard stuff.

with a null hdr check before use (corrupt msg base?)

This reverts commit ebe52737.

This reverts commit 4ce91537.

This reverts commit 33be8662.

gitlab-runner on my Mac mini doesn't have access to /sbbs

We don't build on SunOS anymore, and using LD_RUN_PATH sucks.
Also, it was badly out of date.