ExecutorPodsAllocator fails to identify some excess requests during downscaling

During downscaling there are two kinds of POD requests which can lead to POD deletion as it is identified as excess requests by the dynamic allocation:

• timed out newly created POD requests (which even haven't reached the Pod Pending state, yet)
• timed out pending pod requests

The current implementation fails to delete a timed out pending pod requests when there are not enough timed out newly created POD requests to delete but there are some non-timed out ones.