Multi pool support

[Ryang-21]

• Implements support for multiple pools to be monitored

[mootz12]

There might be some argument as to create N bidder_submitters, one for each filler entry.

However, the odds this makes any meaningful difference to the ability for a bot to fill auctions is like 0, so IMO for now lets keep it like this. Just wanted to leave a comment here incase we opt to do this in the future.

[mootz12]

we don't need to use a timeout

per usage of this class, it caches everything until you rebuild it.

Most of our workflows are on a per ledger basis, so this is OK

[mootz12]

this applies for all the fns in this class

[mootz12]

does this need an error?

Can't it just be a Map<string, Pool>?

      if (cachedPool) {
        if (cachedPool instanceof Pool) return cachedPool;
        else throw cachedPool;
      }

is a bit confusing to me. IMO it's fine as:

    try {
     let cachedPool = this.pool_cache.get(poolId);
      if (cachedPool !== undefined) {
          return cachedPool;
      }
      let pool: Pool = await PoolV1.load(this.network, poolId);
      this.pool_cache.set(poolId, pool);
      return pool;
    } catch (e: any) {
      logger.error(`Error loading ${poolId} pool:  ${e}`);
      throw e;
    }

If this errors, whatever is being processed is gonna stop anyway and wait to be re-tried. If for some reason it doesn't before SorobanHelper is reconstructed, it probably should try and fetch the pool again.