Add log_level parameter to teraslice job.

[busma13]

This PR adds the log_level parameter to a teraslice job.

• Export loglevels from utils/src/Logger
• Add log_level to job-components/src/job-schema
• Within the Worker and ExecutionController constructors, use the log level from the executionContext to set the log level of context.logger before it is used to create a new child logger.
• This child logger will be inherited by all other classes that have a logger within Worker and ExecutionController instances.

Ref: #3498

[godber]

Fix the default problem, and is there a way we could have implemented a test to catch that scenario.

[godber]

Bump sub package versions and teraslice version to 0.90.0 (both top level and subpackage) and consider the inline suggestion

[godber]

Given the check against logLevels I think this test for string might be redundant and less useful. Imaging a user provides a number 5, then they will be told to use a string. Then they put in the string noisy, then it finally tells them the acceptible set of strings. Maybe the next check should test for string and includes(level).

[busma13]

Good point. I will combine the two checks and just have one error message.

[godber]

There's not a whole lot of code here, but since it cross cuts packages and schemas and things we might ask for @jsnoble's input.

[jsnoble]

Talked with @busma13 and asked to put in some comments and double check the log levels are changing when logs are sent to the file, also to put the type log_level in the types package

[busma13]

I added an explanatory comment on each of the constructors that overwrites the log level. I also confirmed that the log_level indicated in the job is written to a log file (all log streams are overwritten with new log level).