Add handling of terminal OS signals

Now <ctrl>-c will use the Terminator for more or less graceful shutdown:

$ lsp-tester @~/work/lisp/lsp-tester/cfg/client.cfg
13:10:35 INF LSP Tester starting
13:10:35 INF Receiver starting for=server
^C13:10:37 WRN Terminal OS signal received signal=interrupt
13:10:37 INF Shutdown svc=Receivers
13:10:37 ERR End of file or broken connection for=server
13:10:37 INF Receiver finished for=server
13:10:37 INF LSP Tester finished

Go can't handle SIGKILL. On Linux kill <pid> sends a SIGTERM so that is handled:

$ lsp-tester @~/work/lisp/lsp-tester/cfg/client.cfg
13:08:01 INF LSP Tester starting
13:08:01 INF Receiver starting for=server
13:08:17 WRN Terminal OS signal received signal=terminated
13:08:17 INF Shutdown svc=Receivers
13:08:17 ERR End of file or broken connection for=server
13:08:17 INF Receiver finished for=server
13:08:17 INF LSP Tester finished

but kill -9 <pid> is not:

$ lsp-tester @~/work/lisp/lsp-tester/cfg/client.cfg
13:08:44 INF LSP Tester starting
13:08:44 INF Receiver starting for=server
Killed

Bug fixes

• Attempt to create backup log lsp-tester.err with log level warn when -logLevel=none is in use.
• Update enumerated values for `flags.Protocol'.
• Use go-utils/app.Terminator to shutdown application.
• Configure Receiver "other" linkages before starting client Receivers to avoid timing issue at startup.
• Minor stylistic tweaks.

Add command LSP

This is a fairly extensive refactoring of lsp-tester in order to support LSPs that are launched as sub-processes and communication via standard input and output.

• Refactoring of Receiver as an interface supporting:
  • TCP protocol which already existed and
  • Sub protocol to support sub-process LSPs.
• New -mode and -protocol flags to support wider variety of test cases.
• Various new flags and flag behavior:
  • configuration files containing flags
  • -fileLevel
• Various bug fixes

Version flag

• fix potential error in showing version data
• add Main/Version which might in some cases show the version tag

Add -version flag.

v1.0.2

Fix version information

Cleanup stuff from Go Report Card

Merge pull request #1 from madkins23/report-card

Cleanup stuff from Go Report Card

Release to public

v1.0.0

Remove development notes

Fix keyword field recognition code

v0.7.1

Fix keyword field recognition code

Keyword format tweaks

v0.7.0

Remove notes.txt

Use only one line per message

• In Nexus mode each message would be logged twice:
  • first from the source to the tester and
  • then from the tester to the receiver.
• Remove this behavior by default so that:
  • there is one log line per message and
  • the tester in the middle is not visible.
• Add flag -logMsgTwice (default false) to regain original behavior.
• The new flag will likely never be used.