op-e2e: Simplify output game creation by auto-deriving rootClaim

[esorense]

Changes:

• Removed rootClaim parameter from StartOutputCannonGame, StartOutputAlphabetGame, and StartPermissionedGame
• Added WithInvalidOutputRoot() and WithOutputRoot() options
• Auto-derive rootClaim via crypto.Keccak256Hash(extraData) internally
• Made CreateBisectionGameExtraData private

Before:

game := factory.StartOutputCannonGame(ctx, "sequencer", 4, common.Hash{0x01})

After:
game := factory.StartOutputCannonGame(ctx, "sequencer", 4, disputegame.WithInvalidOutputRoot())

Updated 27 test instances across 6 files. This aligns output games with the super games pattern, making the API more consistent and harder to misuse.

[ajsutton]

We should also remove the StartOutputCannonGameWithCorrectRoot method (and any similar WithCorrectRoot methods) and just make the default output root value be the valid output root.

I'd also remove the WithInvalidOutputRoot method and consistently use WithOutputRoot to provide an incorrect output root. There's a potential for confusion between "invalid" meaning "not valid to create a game with this root" vs "not the canonical output root". Output root games don't actually have any hashes you can't use as the root claim but super root games do now which creates the potential for confusion when using the term "invalid".

[ajsutton]

This doesn't make sense for output root type games - it's only super root games where the extra data is the preimage of the root claim. 0x000 is an allowed root claim for output root games.