Cleanup foremen/workers relations
Foremen do not report their own core and memory stats.

Conflicts:
	work_queue/src/work_queue_worker.c
Foreman measures disk with workspace
Merge pull request #186 from btovar/foreman-reporting

Commits from Ben and DeVonte include:
1. Clean up the printing of the master-foreman-worker relationships in work_queue_status.
2. Foreman's local disk information is reported to the catalog/master. (the cores and memory is still reported as the aggregate of its workers).
3. Foreman reports cores and memory as 0 in its ready message to master.
4. Fix bug where the disk space of foreman's sandbox was not being used.
Renames local_resources to aggregated_resources.

Also, renames:

work_queue_get_resources to work_queue_aggregate_resources,
work_queue_resources_measure to work_queue_resources_measure_locally.

The motivation is to make the code more readable when dealing with
resources from workers and foremen.
Have ticket test actually try to do something with the ticket.
Put tasks at the back of the only if there is at least one available worker.
This will avoid unnecessarily putting tasks at the back when there are no
connected or available workers.
.
Fix portability problems on Darwin.
Add some helpful debug code.
Other minor fixes (e.g. remove redundant newlines in debug messages).
Bump to 4.1 TRUNK
Cleaned up and simplified the capacity, efficiency, and idle computations.
Simplify default define.
Add const qualifier.
Consolidated status reporting to both catalog and client into queue_to_nvpair.
Removed dependency of work_queue.c on work_queue_catalog.c, which is now solely used by work_queue_pool.c
Distinguished two confusing names:
q->master_link is the tcp connection on which the queue is listening.
foreman_uplink is the tcp connection that connects the foreman to a superior master.
Fixed bug that caused incorrect resources to be reported when
zero workers are connected.
Fixed another instance of confusion between master_link and foreman_uplink.
xml boilerplate
format individual nodes
display child->parent relationships
create xml for stdout redirection if necessary