Implemented several changes to extend context used in UA/SL

Implemented several changes to extend context generic to be used in both shiplogic and uafrica-v3 with support for different sets of claims, improved logger (not used by SL) with color in console or json format, in-memory queue for local testing of API and SQS in one image, etc etc

Related to #2 (closed)

api/README.md

 # TO TEST
 - mage run and local run
-- claims
-- ctx values, read from handler and set in handler then retrieve later in handler
+- claims *& impersonate
 
 # TODO
-- sqs
-- cron
-- combined local service with api,sqs and cron
+- crash dump recover does not log the call stack - impossible to debug
+- sqs local & cloud
+- cron local & cloud
 - use in v3 and shiplogic
-- config for local running
-- db connection
-
-
-- when handler returns an error to indicate HTTP code, then it is wrapped and user gets:
-
-```{"message":"error from handler, because user not found HTTP(404:Not Found), because user does not exist"}``` instead of just:
-```{"message":"user does not exist"}```
-
+- config for local running - from cdk stuff...
+- db connection in app + claims in app
 - api-docs not yet working here - and need to provide HTML option or per-endpoint options at least
+- log as JSON when not running local
+- remove log clutter from API but allow switch on/off or dump on error using log sync...
+- log as JSON - see if crash dump etc are clearly logged as fields, not as part of a string
 
+# Later
 - add path parameters, e.g. /user/{user_id} - make sure it works the same way as lambda does - but we're not using it at present, I assume because the old simple map[][] router did not support it.
-- load config for local running
 - document with examples and templates
-- scheduled tasks from the db or some other scheduler from AWS?
\ No newline at end of file
+- scheduled tasks from the db or some other scheduler from AWS?
+- clone db locally then run with local db not to mess up dev for others
+
+- API test sequences configure & part of docs