deploy uses largeIndexRequestTimeout for both LOW and HIGH priority harvester instances

in the it_conf.xml file one can define:
<largeIndexTimeout>XYZ</largeIndexTimeout>
Deploy should use this value to override the default indexRequestTimeout from settings.xml for LOW priority harvesters

• it seems that both LOW and HIGH priority harvesters get this overridden value
  The deploy unit test is maybe not working properly - at least not testing the scenario we use in production. It should test that two instances on the same harvester machine have different priority and thus gets different indexRequestTimeout values.