Restore request_id to Graveler logs

[arielshaqed]

Also add request_id to some logs to actions. Fixes #4566, and helps push
#2682 towards the finish line.

[arielshaqed]

Tested by running locally manually. I can now see:

• request_id on Graveler logs about branch conflicts, e.g.:

  INFO   [2022-11-20T16:52:05+02:00]pkg/graveler/graveler.go:1785 pkg/graveler.(*KVGraveler).retryBranchUpdate.func1 Retrying update branch                     branchID=main host="localhost:8000" method=POST operation_id=MergeIntoBranch path=/api/v1/repositories/bar/refs/moo/merge/main request_id=bc71651e-1999-419f-8a30-11f3a82bb939 service_name=rest_api try=2
  

• request_id on some actions log lines, notably the "filtering" one, e.g.:

  DEBUG  [2022-11-20T16:50:57+02:00]pkg/actions/service.go:226 pkg/actions.(*StoreService).Run Filtering actions                             host="localhost:8000" method=POST operation_id=Commit path=/api/v1/repositories/bar/branches/moo/commits record="{5mt5qbv13hou1ekh8jqg pre-commit bar s3://treeverse-ariels-test-us/repos/local-bar/ moo moo {1 admin add foo  2022-11-20 16:50:57.826849025 +0200 IST m=+515.643694361 [92d1379d90d81f5da73412137b65594106b3b32fdae34b24b5ec527e7ae24cbd] map[] 0}   }" request_id=e6bb0334-60fd-44f5-ad6e-8e4fb59f4341 service_name=rest_api spec="{pre-commit moo}"
  
  

  • However note that async actions log lines still do not include a request_id; opened Add logging context to actions async Runs #4615 about that.

[nopcoder]

LGTM, require a minor fix to the code documentation.

[nopcoder]

need to fix to 'logger' or 'log' to match the field name

[arielshaqed]

Fixed, thanks! Pulling once tests green.