feat(core): EOA sender validation (EIP-3607)

[sunwavesun]

Changes

• Implemented core logic for EOA validation based on EIP-3607
• Added unit tests to cover EOA validation and preCheck functionality

Cause

This update enhances security by preventing contract accounts from sending transactions directly, aligning with the EIP-3607 standard. It addresses inconsistencies in sender validation logic within the core module. Notably, staking messages are still exempt from the EOA check, as Harmony permits multisig accounts (which are non-EOAs) to send staking messages.

How to Test

• Run make go-test to verify all unit tests pass
• Run go test -run ^TestPreCheck$ github.com/harmony-one/harmony/core for the specific unit test

Notes:

This PR was based on an earlier version (#4840) but has been updated and cleaned up.

[sophoah]

hey @sunwavesun can you add unit test for NewStakingMessage.

[sunwavesun]

@sophoah updated the unit tests to cover NewStakingMessage. The previous unit tests for staking messages are still passing, as well as the rosetta checkers.

[sophoah]

@Frozen thanks for review/approval