Disable profiler objects when APEX uses TAU

[khuck]

When APEX is built/linked with TAU, disable the profiler objects and profiler_listener processing. This would require getting the profile from TAU when requested, but that functionality exists and is just a function call.

Other listeners that depend on the profiler object may have problems. Maybe we create a profiler object without taking a timestamp? And on the stop event, just delete the object rather than queueing it? That way, TAU will handle all the timing, and we don't have duplicate functionality.

[khuck]

I started this work on godzilla, I will put it into a branch, called tau_refactoring.

[khuck]

Nick pointed out that some policies only request the profile once, and then re-use the pointer. This won't work with TAU data, since the data has to be refreshed manually.

[khuck]

Also, need to support inclusive/exclusive, different metrics, etc.