Expand scope of CUPTI activity backend and upgrade cupti_activity component

[jrmadsen]

• Currently the cupti_activity component only collects timing data
• The tim::cupti::activity backend as a result assumes timing data is the only relevant data being extracted
• Also, it forces a synchronize at the end of marker and should be updated to use correlation ID and updated later since this scheme is required by the CUPTI profiler API