Use page guard in trimmed files to reduce state setup size for resources

[bradgrantham-lunarg]

When capturing non-trimmed, page guard will basically determine which resources and which parts of them are dumped in the file. The function that does the writing is WriteFillMemoryCmd which is provided to the page guard functions. This function will write format::MetaDataType::kFillMemoryCommand command in the capture file.

When capturing trimmed, when the trim range begins, all resources (buffers and images) are dumped into the capture file, without the space optimizations we gain from the page guard mechanism. Page guard is not engaged until the trimming range is reached. When that happens all resources will be dumped in the file. Capture manager will write format::MetaDataType::kInitBufferCommand and format::MetaDataType::kInitImagerCommand commands for each resource.

This issue represents a future enhancement in which we would look into using PageGuard in tracking in order to reduce the amount of data written to the state setup block to set up a given resource.