evm: Remove redundant threshold setting in script

[patitonar]

This PR removes an explicit call to INttManager.setThreshold(1) that is not needed given that the threshold was already set to 1 in a previous call to IManagerBase(nttManager).setTransceiver(transceiver); when the first transceiver was added.

native-token-transfers/evm/src/NttManager/ManagerBase.sol

Lines 353 to 379 in 404c0aa

	function setTransceiver(
	address transceiver
	) external onlyOwner {
	_setTransceiver(transceiver);
	_Threshold storage _threshold = _getThresholdStorage();
	// We do not automatically increase the threshold here.
	// Automatically increasing the threshold can result in a scenario
	// where in-flight messages can't be redeemed.
	// For example: Assume there is 1 Transceiver and the threshold is 1.
	// If we were to add a new Transceiver, the threshold would increase to 2.
	// However, all messages that are either in-flight or that are sent on
	// a source chain that does not yet have 2 Transceivers will only have been
	// sent from a single transceiver, so they would never be able to get
	// redeemed.
	// Instead, we leave it up to the owner to manually update the threshold
	// after some period of time, ideally once all chains have the new Transceiver
	// and transfers that were sent via the old configuration are all complete.
	// However if the threshold is 0 (the initial case) we do increment to 1.
	if (_threshold.num == 0) {
	_threshold.num = 1;
	}
	emit TransceiverAdded(transceiver, _getNumTransceiversStorage().enabled, _threshold.num);
	_checkThresholdInvariants();
	}