Increased Court and DK jump logic flexibility

[jaybuidl]

Requested by William.

Goals

• The Court may jump to any Court (not necessarily the parent) immediately on the next round, specified by the currentDK depending on the current court.
• The DK may jump to another DK immediately on the next round, specified by the current DK depending on the current court.
• The DK may jump to another DK when the Court jumps (not before) even if the current DK is still compatible with the destination court.

Overview

DK Configuration

kleros-v2/contracts/src/arbitration/dispute-kits/DisputeKitClassicBase.sol

Lines 61 to 67 in 6d76559

	struct NextRoundSettings {
	bool enabled; // True if the settings are enabled, false otherwise.
	uint96 jumpCourtID; // A non-zero value makes the next round use this court ID. Zero is considered as undefined.
	uint256 jumpDisputeKitID; // A non-zero value makes the next round use this dispute kit ID. Zero is considered as undefined.
	uint256 jumpDisputeKitIDOnCourtJump; // A non-zero value makes the next round use this dispute kit ID ONLY IF the court jumps and `jumpDisputeKitID` is undefined. Zero is considered as undefined.
	uint256 nbVotes; // A non-zero value makes the next round use this number of votes. Zero is considered as undefined.
	}

Examples:

kleros-v2/contracts/test/foundry/KlerosCore_Appeals.t.sol

Line 1055 in 6d76559

jumpCourtID: court3ID, // Jump to sibling Court3, NOT parent GENERAL_COURT

kleros-v2/contracts/test/foundry/KlerosCore_Appeals.t.sol

Line 545 in 6d76559

jumpDisputeKitIDOnCourtJump: dkID3,

Related past changes

#2114
#2110
#1357