Bulletproof the Box class against accidental world corruption and bugs.

In some rare cases the Box's initialize() may be supplied with
coordinates equal to INT_MAX while theoretically being initialized.
Normally this would be harmless, as with every coordinate being
INT_MAX the resulting box's dimensions are zero, however anywhere
where one of the coordinates is actually used in a loop with a
"i <= coord" condition the loop counter will overflow and bad things
will happen, e.g. in FillerFlattener.iteratePattern, where
I encountered this bug, an array will overflow and take down the
whole game with it resulting in a corrupted world. (As broken INT_MAX
coordinates will get saved in NBT tags.)
Removed the config option to always connect pipes. Refactored pipe connections
add ForgeDirection to logic too
fix transport connects
remove general check on transport class
Merge pull request #655 from kouteiheika/master

Bulletproof the Box class against accidental world corruption and bugs.

-Don't really understand, but merged anyway.
Merge branch 'PipeConnectionRefactor' into upstream

Conflicts:
	common/buildcraft/transport/TileGenericPipe.java
Merge branch 'upstream' into 1.5
Merge branch 'PipeConnectionRefactor'

Conflicts:
	common/buildcraft/transport/TileGenericPipe.java
Merge remote-tracking branch 'remotes/upstream/master' into 1.5
clean