No need to query data from TRSS when divide test lists on machine number

[sophia-guo]

There are two ways to divide test lists divideOnMachineNum() and divideOnTestTime(). There is no need to query test time from TRSS for divideOnMachineNum().

Currently when call divideOnMachineNum() TRSS is queried and return no data, which doesn't help test division at all. For example, TCK run are using divideOnMachineNum() and each time TRSS is queried. Either TRSS is unavailable or no data at all, but always takes time and receive unnecessary and confused console output.

[smlambert]

I do not think we should remove the current functionality in the case where the TRSS server is healthy and returning data.

The statement "No need to query for divideOnMachineNum" is only true if test targets are approximately the same size (which is not the case and something we can not guarantee).

Example:
9 test targets, average execution time: TT1 takes 2 hrs, TT2, takes 1 hr, TT3-TT7 take 15 min, TT8-TT9 take 1 min.

Divide with TRSS info.
TT1 -> machine1 runs ~2hrs
TT2 - TT3 -> machine2 runs ~1hr 15min
TT4-TT9 -> machine3 runs ~1hr 2min
Run time of parent ~2hrs

Divide across 3 machines without average execution time information.
TT1, TT2, TT3 -> machine1 runs ~3hrs 15min
TT4, TT5, TT6 -> machine2 runs ~45min
TT7, TT8, TT9 -> machine3 runs ~17min
Run time of parent ~3 hrs 15min

[sophia-guo]

True, test targets might not be the same size.

However for TCK, it might be a special case. TRSS doesn't have any test information to return even if it's healthy ( at least for temurin-compliance). Might be a nice to have feature to turn the query off/on as needed.