DBaaS: MongoDB cluster is in active state after resume

User impact: 

User sees wrong status for 5-10 seconds right after resuming paused MongoDB cluster

STR:

Register Kubernetes Cluster on DBaaS page
Add MongoDB cluster and wait until it's ready
Suspend the MongoDB cluster
Resume the paused DB cluster

Expected result:

Paused > Pending > Active

Actual result:

Paused > Active > Pending > Active

Suggested Implementation:

On list database response return Pending status if there are 0 pods ready

Details:

Recording + HAR attached