Add E2E test verifying behavior when transactions are not gossiped

## Problem

In https://github.com/algorand/go-algorand/pull/4371#discussion_r940496735, we discovered an untested code path in `ledger/internal/eval.go`. Although a unit test was added to fix the thread's issue, it's problematic because there exist other untested scenarios.

It'd be ideal to create a go-algorand E2E test verifying correct behavior + defending against regressions. The challenge is to trigger the code path by adding a node that does _not_ see gossiped transactions.

## Solution

## Dependencies

## Urgency