Restructure and improved logs and audit

Restructure mainly queues to separate consumer from producer, because consumer is a service, but service must be able to produce, which caused cyclic dependencies. Now audit and logs can use a producer to send SQS events, and service can use logs and audits.

Related to #13 (closed)

api/README.md

@@ -204,9 +204,7 @@ API documentation will eventually be generated from doc tags in your structs. Th
 
 # API Logger
 
-API uses the go-utils/logger at the moment. Eventually it will be possible to use other loggers, and customise api logs. Audits can already be customised using ```api.WithAuditor()```.
-
-By default, go-utils/logger writes JSON records. At the start of the example api main function the logger is configured to write console format and log at DEBUG level... more to come on this front too including triggers for full debug in production on selected handlers or specific events, and logging different levels for selected code packages to avoid log clutter without having to remove debug from code.
+API Logs are written from global variables using logs.LogIncomingAPIRequest()
 
 # Router Path Parameters