Description of problem:
There is an API on the capsule that Satellite calls to get an idea of how much that capsule is loaded. This endpoint is terribly inefficient, it completely loads all dynflow execution plans and then counts them, leading to the capsule consuming a lot of memory and eventually getting oom-killed.

Version-Release number of selected component (if applicable):
Probably all currently supported version

How reproducible:
Always

Steps to Reproduce:
1. Have a couple of hosts
2. Run a job which generates a medium amount of output on all the hosts
3. Goto 2

Actual results:
Memory consumed by smart-proxy service grows at a significant rate

Expected results:
Memory consumed by smart-proxy only grows somewhat linearly to the size output from the jobs being run.

Additional info: