Simplify implementation of order API integrations for vendors

Overview: Update existing architecture to allow for additional third parties to easily add routing for their data through edge-orders. Sending it into a FOLIO module they have contributed for the use of mod-orders APIs for creating and possibly updating order records in FOLIO based on work done in their separate system.

Background:
Writing a vendor-specific module (see wiki Configuration based logic) this is where mapping and translation happens between the vendor and FOLIO (mod-orders). Lookups of things like locations, material-types, organizations, etc. will also happen here.
Minor changes in edge-orders to handle proper routing of requests to the proper vendor-specific module (e.g. mod-gobi, mod-ebsconet, etc.). There's essentially a decision tree that looks at the "type" query argument in the request and uses that to proxy the request to the appropriate API, e.g. POST /orders?type=GOBI proxies the request to POST /gobi/orders.

Approach:
Allow for these type → API mappings to be defined via configuration.