Done.

Done.

CASTOR-4749: tapeserverd must NOT treat tapegateway::NoMoreFiles as an error in response to a tapegateway::VolumeRequest

A new unit test has been created for validating that Volume request -> No More Files is not considered as an error.

The code has been changed accordingly. EndNotificationErrorReport is still considered an error.

Conflicts:
	castor/scheduler/diskmanager/activitycontrol.py

Renamed vdqm_CreateRequestForAggregator and vdqm_QueueRequestForAggregator to vdqm_CreateRequest and vdqm_QueueRequest

Conflicts:
	castor/castor.conf

Done.

Created a new unit test to try and reproduce the problem seen here. It did not.
The best explanation we have is a stuck file client. As we totally fail to read data
from the tape, it makes no sense to open a file for which we have no data. So we deferred
the file opening when the first memory block arrives from the tape thread. The outputs of the
unit test showed that the file opening has been successfully deferred.