TrigT1ResultByteStream: Rvalue references proposal

I changes the "set" methods in the ByteStream objects to only accept rvalue references. The intention of this is to force the caller to decide if they should copy or move the object. This would be confusing for most physicists but since this is core software I think we should enforce rigour. This should reduce a large amount of memory copying and maybe memory fragmentation.