deepify list is very slow and uninformative

It took 35 seconds to show me something. Let's change that by displaying more info faster (e.g. Querying Tagging API to compile the list of all applications, Querying [service_name] to retrieve the list of all resources), as well as optimize where is possible. See my test below:

MitocGroup:~ eugene$ time deepify list
10:42:48 GMT-0500 (CDT)  To get more details, run deepify list --depth=2 or deepify list --depth=3

#1. ATM Api (ebf6f3ce) | using 11 cloud services 
    -------------------------------------------- 


#2. ATM Api +account (5347f79a) | using 13 cloud services 
    ----------------------------------------------------- 


#3. My Custom Web App 59a59b0775a22b6374595c8ebf525f1c (959f2268) | using 11 cloud services 
    --------------------------------------------------------------------------------------- 


#4. My Custom Web App cb5193fee11d7111ff6de88cd12d62c7 (770efe66) | using 11 cloud services 
    --------------------------------------------------------------------------------------- 


#5. hello.deep.mg (370b9c50) | using 10 cloud services 
    -------------------------------------------------- 


#6. todo.deep.mg (55182282) | using 11 cloud services 
    ------------------------------------------------- 


#7. unknown application | using 2 cloud services 
    -------------------------------------------- 


#8. www-dev.adtechmedia.io (430f1fff) | using 12 cloud services 
    ----------------------------------------------------------- 


#9. www.adtechmedia.io (57ad5dd8) | using 12 cloud services 
    ------------------------------------------------------- 


#10. www.deep.mg (41ae5689) | using 9 cloud services 
    ----------------------------------------------- 


#11. www2_serverlessConf (7bb794bc) | using 11 cloud services 
    -------------------------------------------------------- 

 

real	0m35.187s
user	0m1.989s
sys	0m0.233s

Start by locating the implementation of the deepify list command and reproduce the issue with deepify list, recording its response time and output. Trace how it queries the Tagging API and cloud services. Done means the command returns more useful application and resource information faster than the reported 35 seconds, with deeper output still available through --depth=2 or --depth=3.