Add the EVM GW version to log lines

[m-Peter]

Closes: #594

Description

For each log line, we include the released version that is running:

{
    "level": "debug",
    "version": "v0.36.4",
    "component": "API",
    "id": 4,
    "jsonrpc": "2.0",
    "method": "eth_call",
    "params": [
        {
            "from": "0x658bdf435d810c91414ec09147daa6db62406379",
            "gas": "0x76c0",
            "gasPrice": "0x0",
            "input": "0xc6888fa10000000000000000000000000000000000000000000000000000000000000006",
            "to": "0x99466ed2e37b892a2ee3e9cd55a98b68f5735db2",
            "value": "0x0"
        },
        "latest"
    ],
    "result": "0x000000000000000000000000000000000000000000000000000000000000002a",
    "time": "2024-09-30T09:38:33+03:00",
    "message": "API response"
}

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the standards mentioned here.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

Summary by CodeRabbit

• Bug Fixes

  • Improved error handling for COA signer creation, providing clearer error messages when key configurations are missing.

• Chores

  • Enhanced logging functionality to include API version in log outputs for better traceability during initialization and server startup.

[coderabbitai]

Walkthrough

The changes in the pull request enhance the logging functionality and error handling within the Bootstrap struct in bootstrap/bootstrap.go. The logger now includes a version string, improving log clarity. The StartAPIServer method has been updated to provide better error messages for COA signer creation, while the overall structure and flow of the methods remain unchanged.

Changes

Files	Change Summary
bootstrap/bootstrap.go	Updated logger initialization to include version string; enhanced error handling in StartAPIServer for COA signer creation.

Assessment against linked issues

Objective	Addressed	Explanation
Add Gateway Software version to logs (#594)	✅

Poem

In the meadow where rabbits play,
Logs now shine with version's ray.
Errors caught with gentle care,
A server's song fills the air.
Hops of joy, we celebrate,
Changes sweet, we elevate! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[janezpodhostnik]

LGTM

Tanks