pre-populate code cache from provided profiling data

In some attach scenarios (currently only fully supported with static DR in a start/stop type model) we want to pre-populate the code cache on the side so when we trigger the attach we can avoid the cost of building the cache up. This issue covers creating some kind of interface where a list of basic block start tags obtained from profiling can be passed to DR to create a pre-warmed cache.