Remove print calls in tests

[rdimaio]

Doing a quick search for print( in tests/ returns more than 700 instances of printing in tests, e.g. as seen here:

rucio/tests/test_replica_recoverer.py

Lines 206 to 217 in 767dbc5

	if replica['name'] == self.tmp_file7.name:
	print("Updating replica state as unavailable: " + replica['rses'][self.rse4recovery_id][0])
	update_replica_state(self.rse4recovery_id, self.scope_declarebad, self.tmp_file7.name, ReplicaState.UNAVAILABLE)
	if replica['name'] == self.tmp_file9.name:
	print("Updating replica state as unavailable: " + replica['rses'][self.rse4recovery_id][0])
	update_replica_state(self.rse4recovery_id, self.scope_declarebad, self.tmp_file9.name, ReplicaState.UNAVAILABLE)
	if replica['name'] == self.tmp_file11.name:
	print("Updating replica state as unavailable: " + replica['rses'][self.rse4recovery_id][0])
	update_replica_state(self.rse4recovery_id, self.scope_declarebad, self.tmp_file11.name, ReplicaState.UNAVAILABLE)
	if replica['name'] == self.tmp_file13.name:
	print("Updating replica state as unavailable: " + replica['rses'][self.rse4recovery_id][0])
	update_replica_state(self.rse4recovery_id, self.scope_declarebad, self.tmp_file13.name, ReplicaState.UNAVAILABLE)

Printing is useful for debugging, but once a test has been written and has the proper assertions, print statements should likely be removed.

print affects performance, as tested here: https://stackoverflow.com/questions/13288185/performance-effect-of-using-print-statements-in-python-script - we might be able to gain some performance in test speed by removing these calls.