vendor path-to-regexp

[tbeseda]

This branch now vendors path-to-regexp to avoid Arc hydrate grabbing the latest when a consumer of Enhance deploys.

See below for historical context.

previous discussion

Don't merge! Pretty sure bad things will happen... 😨

At the moment when Arc hydrate treeshakes the Enhance any-catchall route, there is not package.json so it will install the latest of any discovered package.

This has worked fine because most dependencies here are stable. However, there's a rewrite of path-to-regexp in a major version, v8.0.0.
The new version is picked up by hydrate this route blows up since the API changed.

You can replicate this locally:

1. any Enhance app
2. run npx @architect/architect hydrate (this happens on deploy to AWS or Begin)
3. see that hydrate does work on node_modules/@enhance/arc-plugin-enhance/src/http/any-catchall/
4. navigate to that dir + /node_modules/path-to-regexp/package.json
5. it's v8.0.0
6. that's bad, Enhance wants v6.2-ish

I could use the updated v8 of path-to-regexp, but that doesn't really fix the problem.

Instead, I think we should give hydrate a package manifest to work with.

However, I think we've done this before. I believe this would then mean that route would not get dependencies (via treeshaking; which is disabled when a manifest is present) for userland code in node_modules/@architect/views. But I can't recall.

Another option is to change how hydrate works for plugin-provided Lambdae source directories. It could reference plugin-space package.json for the version. But with @architect/views (which is app/) it does a merge? idk could be messy.

Also relevant: #87

Let's discuss.

In the meantime I will update our router implementation to use the new path-to-regexp