Backport release/v6.6: Require absolute path for evmone lib

[seidroid]

Backport of #3668 to release/v6.6.

[cursor]

PR Summary

Low Risk
Small validation change in EVM library path resolution with tests; no change to default /usr/lib or in-tree fallback behavior when the env var is unset.

Overview
Enforces that SEI_EVMONE_LIB_DIR must be an absolute path when set; relative values (e.g. .) now fail fast with a clear error instead of being used in library resolution.

This aligns operator overrides with the existing intent to load evmone via a fixed absolute path and SHA-256 check, reducing ambiguity about which directory is trusted. Tests cover rejection of relative overrides and successful resolution from an absolute temp directory.

^{Reviewed by Cursor Bugbot for commit eb3fe0d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Jun 30, 2026, 10:43 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.02%. Comparing base (ae6a51e) to head (eb3fe0d).

Additional details and impacted files

@@               Coverage Diff                @@
##           release/v6.6    #3669      +/-   ##
================================================
- Coverage         58.90%   58.02%   -0.89%     
================================================
  Files              2225     2151      -74     
  Lines            183480   174935    -8545     
================================================
- Hits             108086   101505    -6581     
+ Misses            65691    64422    -1269     
+ Partials           9703     9008     -695     

Flag	Coverage Δ
sei-chain-pr	37.14% <100.00%> (?)
sei-db	70.41% <ø> (ø)
sei-db-state-db	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
giga/executor/lib/evmlib.go	62.85% <100.00%> (+8.31%)	⬆️

... and 101 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[claude]

Straightforward backport of #3668 to release/v6.6.

Extended reasoning...

Overview

This PR backports #3668 to the release/v6.6 branch. The change adds a check in resolveLibPath() that rejects SEI_EVMONE_LIB_DIR values that are not absolute paths, plus two unit tests covering the rejected-relative and accepted-absolute cases.

Security risks

None introduced. The change tightens a security boundary by ensuring operator overrides for the evmone library directory must be absolute paths, preventing ambiguity in dynamic library resolution. The existing SHA-256 integrity verification still applies regardless.

Level of scrutiny

Low. This is a mechanical backport of an already-merged change to a release branch. The diff is identical in intent to the original PR, the surface area is tiny (3 added lines in production code), and the new tests directly exercise both branches of the new validation.

Other factors

The change matches the documented intent in the existing comment block on libDirEnv ("It must be an absolute path..."). Test coverage is adequate for the new behavior.