chore: remove Ctx field from FinalizeBlockRequest

The context fields on other request types make sense because we may need
to interrupt, say, a prevote decision due to falling behind. But there
are no circumstances, other than process shutdown, where we would want
to interrupt a block finalization.

tm/tmapp/requests.go

@@ -1,8 +1,6 @@
 package tmapp
 
 import (
-	"context"
-
 	"github.com/rollchains/gordian/tm/tmconsensus"
 )
 
@@ -37,10 +35,6 @@ type InitChainResponse struct {
 //
 // Consumers of this value may assume that Resp is buffered and sends will not block.
 type FinalizeBlockRequest struct {
-	// TODO: Ctx should probably be removed.
-	// The only time a finalize request would be interrupted would be a root context cancellation.
-	Ctx context.Context
-
 	Block tmconsensus.Block
 	Round uint32
 

tm/tmengine/internal/tmstate/statemachine.go

@@ -416,7 +416,6 @@ func (m *StateMachine) sendInitialActionSet(ctx context.Context) (
 
 		// This is a replay, so we can just tell the app to finalize it.
 		finReq := tmapp.FinalizeBlockRequest{
-			Ctx:   ctx, // Is this the right context? Do we even still need context?
 			Block: update.CB.Block,
 			Round: update.CB.Proof.Round,
 

tm/tmengine/internal/tmstate/statemachine_test.go

@@ -293,8 +293,6 @@ func TestStateMachine_initialization(t *testing.T) {
 		// Now the state machine should make a finalize block request.
 		req := gtest.ReceiveSoon(t, sfx.FinalizeBlockRequests)
 
-		require.NotNil(t, req.Ctx)
-		require.NoError(t, req.Ctx.Err())
 		require.Equal(t, pb1.Block, req.Block)
 		require.Zero(t, req.Round)