Check if no-op cali macros are defined first

[chapman39]

Haven't tested with lido, but it does pass tests when benchmarking is disabled.

Fixes #1164

[white238]

I spoke with @chapman39 about this yesterday. This is my fault. I shouldn't have advised him to remove our Serac specific macros. I forgot the original reason we did this. We should put our project specific ones back so that it does the following:

• Allows our downstream users to selectively turn off timings in Serac so it doesn't pollute their timings.
• Doesn't redefine macros that will conflict with others, namely Caliper.

This should not be merged and @chapman39 knows to just undo the important part of the last Caliper macro PR. Luckily it's just copy/pasting and search/replace. We should put a comment in profiling.hpp to explain why we map these defines so I don't forget in the future and repeat this cycle.