Workflow for ZWEL messages

[Martin-Zeithaml]

build/zwelMessages.js

JS definition of ZWEL messages - move out of the header file to keep it small.

build/buildZwelMessages.js

Two functions

1. Run without any parameter to get the MD of the ZWEL messages.
2. Run with --check parameter to test if messages are unique and documented. This check is run in a new workflow.

Others

New Workflow and Readme file with some details.

How it works

New message and doc update is made, run the script to generate MD:

PS C:\Users\Martin\Git\zowe\launcher\launcher.workflow\build> node .\buildZwelMessages.js
# Error Message Codes

The following error message codes may appear on Zowe Launcher SYSPRINT. Use the following message code references and the corresponding reasons and actions to help troubleshoot issues.

## Zowe Launcher informational messages

### ZWEL0001I

  component %s started

  **Reason:**

  The component `<component-name>` was started.

  **Action:**

  No action required.

### ZWEL0002I

  component %s stopped

  **Reason:**

  The component `<component-name>` was stopped.

  **Action:**

  No action required.
...

New workflow is triggered automatically for each pull request.

  Build and Test Workflow / build-test (pull_request)
  Build and Test Workflow / build-test (pull_request) Successful in 1m
+ Build and Test Workflow / check_messages (pull_request)
+ Build and Test Workflow / check_messages (pull_request) Successful in 6s
  Build and Test Workflow / check-permission (pull_request)
  Build and Test Workflow / check-permission (pull_request) Successful in 3s
  DCO
  DCOSuccessful in 1s — DCO

Small test here.