refactor(voyager): rename consensus modules to finality modules

[marvelshan]

Which issue does this PR close?

closes #4374

Overview

This PR renames the voyager/modules/consensus directory to finality and updates all related package names and references to better reflect their actual functionality.

Why

As identified in issue #4374, the current "consensus" naming is a legacy artifact from an earlier design. These modules now only provide information about finality rather than handling the full consensus process. This renaming improves code clarity and removes potential confusion for developers.

Implementation Details

• Renamed directory: voyager/modules/consensus → finality
• Updated package names in all module Cargo.toml files:
  • voyager-consensus-module-X → voyager-finality-module-X
• Updated all references to these modules throughout the codebase
• Updated trait names and related implementations where applicable

Modules Affected

• arbitrum
• berachain
• bob
• cometbls
• ethereum
• movement
• tendermint
• trusted-evm

[vercel]

@marvelshan is attempting to deploy a commit to the unionbuild Team on Vercel.

A member of the Team first needs to authorize it.

[cor]

Hey @marvelshan , can you please ensure ci passes?

[marvelshan]

Sure! I'll take a look and make sure CI passes. Thanks for the heads-up!

[benluelo]

you'll need to run cargo check to update the Cargo.lock. also please rename the traits as we discussed in the issue

[marvelshan]

Hi @benluelo , I encountered a problem during the test execution in the development environment. The test consistently times out, and I noticed some recurring errors in the logs. Here are the key points:

1. Test Timeout

   The test terminates with the message:

   timeout reached; test terminating...
   

   It seems the test is unable to complete within the expected time.

2. DNS Resolution Errors

   I also observed multiple DNS resolution errors in the logs, such as:

   [resolver] failed to query external DNS server
   error="read udp 172.18.0.10:59231->10.0.2.3:53: i/o timeout"
   

   This suggests that the environment is unable to resolve certain domain names (e.g., redis-db).

3. Virtual Machine Termination

   The virtual machine running the tests is being terminated with the following message:

   kill machine (pid 9)
   qemu-kvm: terminating on signal 15
   

Do you have any suggestions on where I should start looking to resolve this issue? I'm especially wondering whether this could be related to the network configuration, the DNS resolver setup, or something in the test environment that causes the VM to be killed prematurely.

Thanks in advance for your guidance!

[benluelo]

don't worry about the CI issues for now, the timeouts etc are unrelated to this PR. you will, however, need to reword your latest commit.

[marvelshan]

@benluelo Thanks so much for your help and patience. I spent some time setting up the development environment due to compatibility issues between macOS and Nix. Since I’m not very familiar with Nix, I followed the project documentation and ended up using OrbStack to create a NixOS VM. There were some hiccups during the setup—like missing dependencies and OpenSSL build errors—but I managed to resolve them eventually. I really appreciate your guidance throughout this process. I’ve learned a lot from working on this PR, and I’m truly sorry for the repeated force-pushes that kept triggering CI.

[benluelo]

you need to sign all of your commits, and reword all commit messages to follow conventional commits as per our contributing guide

[marvelshan]

I have signed all commits and updated the commit messages.

[benluelo]

thanks!

[marvelshan]

@benluelo Hi, I’ve just completed this issue and the related PR. I’m interested in learning more about the Union project and would love to continue contributing. I noticed there are some issues tagged as Easy and also saw the current issue @unionlabs/union/issues/4360. Do you have any recommendations on which issues I should work on next, or is it fine to pick any that interest me? If there are any issues you think would be especially suitable for someone new to the project, I’d appreciate your suggestions. Thank you!

[benluelo]

4360 is a good simple one if you're interested. i'll write more of an explanation in the issue

[marvelshan]

Thanks. Appreciate it!