Create 'maproulette-request-id' for http requests

[ljdelight]

MapRoulette will log requests to an access log appender and include a generated maproulette-request-id log marker and include it in the response header for clients to debug future issues. Note that clients are responsible for providing the maproulette-request-id in issues.

This change also includes minor fixes to

• remove deprecated logger references from application.conf (resolving Remove logger references from conf files -- it's not supported and does nothing #1085) and
• update to use an async log appender (resolving Consider using an asynchronous logback appender #1083)

Here's what the updated logger output looks like in intellij (logback-dev.xml) loading the /dashboard for a logged in user. The response header maproulette-request-id exists and it does match the logs

This is what it looks like on staging (logback.xml) loading the /dashboard for a logged in user. The response header maproulette-request-id does match the logs:

Not all log messages include the maproulette-request-id and will show an empty [] like so:

06:08:28.497 INFO  [b652b459-682a-4b29-b093-76f2a9aaa0e6][application-akka.actor.default-dispatcher-25][AccessLogger] - Request 'GET /api/v2/user/whoami' [org.maproulette.framework.controller.UserController.whoami] 1ms - Response 401
06:08:48.485 INFO  [][application-akka.actor.default-dispatcher-38][org.maproulette.jobs.SchedulerActor] - Scheduled Task 'Sending Immediate Notification Emails': Starting run
06:08:48.489 INFO  [][application-akka.actor.default-dispatcher-38][org.maproulette.jobs.SchedulerActor] - Scheduled Task 'Sending Immediate Notification Emails': Finished run. Time spent: 4ms

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication