Disabling pectra assertoor - they are neither complete nor stable for
devnet-5

Co-authored-by: alex.sharov <AskAlexSharov@gmail.com>

Earlier only the main hive output was displayed on the workflow page.
This would allow downloading the full logs, and viewing with `hiveview`

Porting from the workflows to makefile for local testing. Benefits:
- Hiveview
- Faster execution of tests
- Easier to execute for a developer on local quickly

Fix issues like header hash mismatch in hive tests for pectra-devnet-5
`RequestData` refers to the raw output from the various different
requests contract, in the rest of the code

- Fix an issue where after the refund the gasUsed could go below floor
gas
- Update spec tests for devnet-5 to release 1.2.0
- Update spec test version in Hive-EEST

See #8171
and Previous PR which put this into `eth_` api -
#11888

Fixes issues where config files have some values and not all, or empty
values for forks.

Note: This config is picked up for custom (unlisted) networks after
`init` cmd is run using a correctly formatted `genesis.json` file (see
[pectra-devnet-5
gensis](https://github.com/ethpandaops/pectra-devnets/blob/master/network-configs/devnet-5/metadata/genesis.json)
file for example)

…3574)

A recent [RLP related
commit](https://github.com/erigontech/erigon/pull/12869/files#diff-ec3e5ec81bd7c4746ee5d895260767e2282f268684ffc0de73d4a7018975493c)
created a uint256 encoding that assumes len = 32 for the passed in
buffered byte array. However, this PR doesn't fix any inherent issues
with [that approach](#12869)
itself. This PR fixes one issue found in `pectra_devnet_5` that creates a
mismatched recovered signer address.