CircleCI: fix l2blob tests and op-program-compat

[syntrust]

Origin log can be found here
The reason is that l2GenesisBlobTimeOffset is not set.

After "l2GenesisBlobTimeOffset": "0x0", is applied, another error occurs due to empty BlobBaseFee:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x549d37]

goroutine 1 [running]:
math/big.(*Int).Mul(0xc006c6f218, 0xc006c6f1f8, 0x0)
        /home/circleci/.mise-data/installs/go/1.22.7/src/math/big/int.go:194 +0x97
github.com/ethereum/go-ethereum/core.(*stateTransition).innerExecute(0xc006c6f440)
        /home/circleci/go/pkg/mod/github.com/!quarkchain/op-geth@v0.0.0-20250217080034-97596a48ef97/core/state_transition.go:871 +0x10ca
github.com/ethereum/go-ethereum/core.(*stateTransition).execute(0xc006c6f440)
        /home/circleci/go/pkg/mod/github.com/!quarkchain/op-geth@v0.0.0-20250217080034-97596a48ef97/core/state_transition.go:666 +0xf7
github.com/ethereum/go-ethereum/core.ApplyMessage(0xc005220000, 0xc00047b2c0, 0xc0043025d8)

The issue fixed after vmenv.Context.BlobBaseFee is set in op-program/client/l2/engineapi/block_processor.go.
This also fixes op-program-compat as the same root cause.

[blockchaindevsh]

And looks like this change is also unnecessary since it's handled in the test here. The l2blob tests can already pass in the latest op-e2e branch.

[syntrust]

Still fails without useSoulGasToken set

[blockchaindevsh]

I mean l2GenesisBlobTimeOffset is not needed, this is what this PR is changing, right?

[syntrust]

Sorry I meant l2GenesisBlobTimeOffset

[blockchaindevsh]

Looks like it's failing because we changed require.ErrorContains to require.NoError in this PR: ethstorage#140 . Maybe we can revert this change since l2 blob is not enabled by default and only enabled in the l2 blob e2e test. This way we don't need to touch the tests of upstream.