Remove queue prefetching from component service queues

[jrobble]

Prefetching behavior can result in starving services in certain situations, resulting in inefficiencies.

For example, If two services are available to process two sub-jobs (one message in the queue for each), the first service may start consuming one sub-job and ActiveMQ may dispatch the next sub-job to the same service as part of the pre-fetching behavior. The second service is then starved. Optimally, the second service should be processing a sub-job at the same time as the first service.

A similar situation happens when only one service is running and a second service becomes available after ActiveMQ dispatches the second sub-job to the first service as part of pre-fetching. Users will often bring up new service instances to distribute the workload. The workload will not be distributed in this scenario. Once this issue is resolved it should.

Note that in the past setting pre-fetch to 0 caused ActiveMQ/messing errors/issues. Be on the lookout for those.

This issue is related to #647.