Additional authz_time, authz_count, url in the logs

It would be useful while debugging to get the same request times specifically the authz_time and authz_count and the url being used by the http request in the logs for failed requests as the successful requests.

A successful request:

2019-04-16T22:35:20Z erchef@127.0.0.1 method=GET; path=/organizations/support/groups/admins; status=200; req_id=g3IAA2QAEGVyY2hxMjcuMC4wLjECAAAJrQAAAAIAAAAA; org_name=support; couchdb_groups=false; couchdb_organizations=false; couchdb_containers=false; couchdb_acls=false; 503_mode=false; couchdb_associations=false; couchdb_association_requests=false; req_time=21; rdbms_time=10; rdbms_count=3; authz_time=6; authz_count=1; user=pivotal; req_api_version=1;
2019-04-16T22:35:20Z erchef@127.0.0.1 method=PUT; path=/organizations/support/groups/admins; status=200; req_id=g3IAA2QAEGVyY2hlZMjcuMC4wLjECAAAJ1wAAAAIAAAAA; org_name=support; couchdb_groups=false; couchdb_organizations=false; couchdb_containers=false; couchdb_acls=false; 503_mode=false; couchdb_associations=false; couchdb_association_requests=false; req_time=41; rdbms_time=29; rdbms_count=4; authz_time=6; authz_count=1; user=pivotal; req_api_version=1;

Failed request:

2020-01-28T15:42:39Z erchef@127.0.0.1 method=GET; path=/organizations/orgname/nodes/chefnode; status=500; req_id=g3IAA2QAEGVyY2hlZkAxMjcuMC4wLjECAAA54gAAAAIAAAAA; org_name=explms; couchdb_groups=false; couchdb_organizations=false; couchdb_containers=false; couchdb_acls=false; 503_mode=false; couchdb_associations=false; couchdb_association_requests=false; req_time=4008; rdbms_time=1; rdbms_count=3; user=chefuser; req_api_version=1;

No source files or tests are named. Start by tracing the request logging path that produces the successful and failed log formats shown in the issue, then identify where authz timing and count are recorded. Done means failed-request logs include authz_time, authz_count, and the HTTP request URL consistently with successful requests, with coverage for both outcomes.