Add ability to programmatically determine what objects are included in a cache policy.

Using a policy has exponentially reduced the time to complete the full cache refresh (from ~ 3 hours to just over 1 hour). However, there is no way to determine which views/objects have been added to a policy, thus managing the cache refresh process has become a chore.

We have some cached objects that have to be refreshed daily, some just once/week and others that can't be part of a policy (incremental, procedures, etc). Without knowing which views are part of the policy, I've been required to create a hack by adding the word "policy" to the annotation of each view in a cache policy. If I forget to put the word in, the cache refresh process tries to refresh it independently and it fails, causing the entire refresh process to fail. If I forget to remove it, and I've removed it from the cache policy, it doesn't get refreshed at all.

We are required to use an external scheduling/workflow manager (Control/M, aka ECS) to manage our cache refreshes. Using a script called by ECS, we collect a list of cached objects, then loop through them, passing in the full path to /lib/resource/RefreshResourceCacheSynchronously(). 

If I had the ability to see identify objects that are part of a policy, the cache refresh process can be fine tuned and will run much more efficiently. Developers won't have to remember that the word 'policy' has to be added, or removed whenever an objects is added or removed from a cache policy.