refactor: refactor log

[binbin-li]

Description

What this PR does / why we need it:

1. Add an internal logger util that initializes logger for Ratify and configures the context with trace-id either from requests or auto-generated.
2. Refactor Executor, Server and Store to use this logger util instead of Logrus directly.
3. Add formatter and requestHeaders to the helm chart value so that users can configure the logger.
4. Add a doc for logger.

This is the first PR which just introduced the basic new logging framework to Ratify. There will be a following PR that refactors most logging lines to use the new logger util.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #972 #963

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
Added unit tests.
A screenshot of local testing, all logs within a request have the same trace-id and have component-type set as well.

Checklist:

• Does the affected code have corresponding tests?
• Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
• Does this introduce breaking changes that would require an announcement or bumping the major version?
• Do all new files have appropriate license header?

Post Merge Requirements

• MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

[codecov]

Codecov Report

Patch coverage: 66.36% and project coverage change: +0.16% 🎉

Comparison is base (85a5803) 58.16% compared to head (aa5776a) 58.32%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1008      +/-   ##
==========================================
+ Coverage   58.16%   58.32%   +0.16%     
==========================================
  Files          91       92       +1     
  Lines        5448     5529      +81     
==========================================
+ Hits         3169     3225      +56     
- Misses       1965     1989      +24     
- Partials      314      315       +1     

Files Changed	Coverage Δ
cmd/ratify/cmd/discover.go	17.64% <0.00%> (-0.54%)	⬇️
cmd/ratify/cmd/referrer.go	29.13% <0.00%> (-0.60%)	⬇️
cmd/ratify/cmd/resolve.go	32.65% <0.00%> (-2.13%)	⬇️
cmd/ratify/cmd/serve.go	38.09% <0.00%> (-4.77%)	⬇️
cmd/ratify/cmd/verify.go	61.84% <0.00%> (-2.55%)	⬇️
cmd/ratify/main.go	25.00% <ø> (-37.50%)	⬇️
config/config.go	51.89% <0.00%> (-4.27%)	⬇️
pkg/referrerstore/oras/oras.go	69.03% <44.44%> (+0.20%)	⬆️
pkg/executor/core/executor.go	89.00% <50.00%> (ø)
httpserver/handlers.go	74.61% <66.66%> (+0.26%)	⬆️
... and 2 more

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[susanshi]

left some suggestion around documentation. thanks!

[FeynmanZhou]

PTAL

[susanshi]

Looks good to me. thanks binbin!