Add Support For Concurrent Account-Based Resource Searches When Running With AWS Org Support

[magneticstain]

IP2Cr supports searching through all AWS Orgs accounts. For large organizations, that can mean a lot of accounts. In order to keep with the IP2CR tenancy of maximum speed, and ultimately to improve the user experience, we should add support for running concurrent resource searches, each working on a different account.

---

Architecture options:

1. Start a pool of X amount of threads. Each thread is assigned an account, cycling through each if number of accounts > X
2. Start a pool of X amount of threads. For each account, send the result set from AWS to be processed by each thread
3. Start a pool of X amount of threads. Each thread is assigned an account, cycling through each if number of accounts > X. For each account thread, Y number of threads is created to process the resource set in batches. Essentially 1 + 2

[magneticstain]

I think we should start with implementing option 1, as it's the most simplest and straightforward option. Then, we can look into implementing 3 at a later date to potentially increase processing speed, at the cost of additional complexity.

[magneticstain]

Additional architecture details:

1. Create a buffered receive channel set to receive 1 object
2. Create a go routine for each account search, sending the channel object as a param
3. In the secondary function, send the matching resource object via the channel, if found
4. In the primary function, listen on the channel for a return value
5. If value is returned, proceed. Otherwise, wait until all go routines are complete