Fix some multiblock placements aborting too early

[Lyfts]

Closes GTNewHorizons/GT-New-Horizons-Modpack#18510

This problem arises when the multiple survivialBuildPiece() are += in survivalConstruct() since returning anything below 0 would previously cause the preview construction to abort.

A possible example for the YottTank with some edits to illustrate the point

    public int survivalConstruct(ItemStack stackSize, int elementBudget, ISurvivalBuildEnvironment env) {
        if (mMachine) return -1;
        int built = 0;
		// This piece is finished which causes built to be -1 
        built += survivialBuildPiece(YOTTANK_BOTTOM, stackSize, 2, 0, 0, elementBudget, env, false, true); 
        int height = 15;
		
		// This piece is also finished meaning built is now -2
        built += survivialBuildPiece(YOTTANK_TOP, stackSize, 2, height + 2, 0, elementBudget - built, env, false, true);

		// 14 of these were already finished and 
		// The last piece only placed a hatch in this round (which are always placed individually)
		// The return value ends up being -15 in this case
        while (height > 0) {
            built += survivialBuildPiece(YOTTANK_MID, stackSize, 2, height, 0, elementBudget - built, env, false, true);
            height--;
        }

		// returns -15 which causes the construction to abort despite not being finished.
        return built;
    }

Previously we fixed that by adding if (built > 0) return built; after most survivialBuildPiece() but that's kinda annoying and unnecessary, especially since we can check whether something was actually placed in the world to more reliably determine whether construction should stop.