Flatten config structure

[andykais]

an alternative structure for the config, one that is more flat, less nested.

const config = {
  flow: [
    scraper1,
    scraper2,
    ...
  ]
}

• [ ] make parsed tag names in tests more obvious which comes first
• [x] rename make in make-conditional-waiting-joins and make-dynamic-level order to compile
• [edit] no longer needed since merge works[ ] make unique scraper keys separate from scraper names
  • this would allow us to reuse names in different places. Currently there can only be one flat config def for a scraper name. reusing names flat out wont work.
  • if we do not do add this feature, we need to disallow reusing scraper names
• [edit] not relevant since the order leveling was removed in favor of grouping scrapers [ ] add test with 1000s of values. I have discovered that ~1000 scrapers will cause some maximum call stack errors. Its possible that a ton of values will not play nice with this design
  • might be worth comparing the old design to this one in terms of max call stack errors.
• closes https://github.com/andykais/scrape-pages/issues/36

[andykais]

theres an important difference in the data flow. Before, data only flew RIGHT and DOWN (scrapeEach array and scrapeEach). Now, there is a third direction. "DIAGONAL-LEFT". E.g. data can hit a branch, then merge back into the downward stream. Its causing a pretty big change in the sql ordering so I want to know if its worth it. The real world use case is, we have multiple places where a single type of data needs to be downloaded/parsed. E.g. traverse several different pages to get all the image links on a site. It could be important to be able to grab all those scrapers at once with the querier.

What I do like about this: its a really intuitive syntax, easy to wrap your head around. E.g.

[
  {
    scraper: gallery,
    branch: [[pageA], [pageB]]
  },
  downloadImage
]

what I dont like about this: the sql ordering isnt that smart. Before I could assume that I was dealing with a tree data structure. Now Im dealing with a one way graph. Its much harder to reason about order in this case

gallery - pageA
       \        \
        pageB -  downloadImage