feat(hook): add allowlist hooks for pre-block transaction and contract filtering

[powerslider]

Extend hook.Points with CanExecuteTransaction, mirroring params.RulesAllowlistHooks so consumers can use a single concrete type for both SAE and libevm hooks. Call CanExecuteTransaction via hooks in worstcase.ApplyTx() to exclude hook-rejected transactions before block inclusion, preventing fatal errors in the execution
loop.

• Add CanExecuteTransaction to hook.Points and hookstest.Stub.
• Call CanExecuteTransaction in worstcase.State.ApplyTx() instead of through libevm rules hooks.
• Remove dead rules field from worstcase.State.
• Add TestCanExecuteTransactionHook in worstcase package verifying blocked senders are excluded and state is not modified.
• Add TestCanCreateContractSoftError confirming CanCreateContract rejection produces a failed receipt, not a fatal crash.

Signed-off-by: Tsvetan Dimitrov (tsvetan.dimitrov@avalabs.org)

[powerslider]

@ARR4N @StephenButtolph I am open to all types of comments and feedback here since this was my first time developing logic around libevm hooks and running them on the SAE side. I've tried my best to simulate the hook validation scenarios and I think that it is correct, but I might be missing something so your feedback here would be invaluable 🙏

[ARR4N]

We can't register any libevm extras in SAE because that precludes consumers from doing the same themselves. Even if we provided "piggyback" hooks to allow registration via SAE, every single change to libevm would have to be replicated here.

I recommend extending hook.Points to replicate the two allowlist hooks identically (the provider of the implementation can then use the exact same concrete implementation for both libevm and SAE hooks).

Why this should be merged

Check #152

Please don't refer to GitHub-specific entities in PR descriptions in lieu of details. It's OK to include them to trigger events (e.g. Closes <#>) but the descriptions become git commits and need to be self-contained.

[powerslider]

@ARR4N yes now I recalled that you mentioned that SAE should not register libevm hooks. It slipped my radar, sorry. I will adapt the implemntation via hook.Points.