Configuration based request routing

Overview

It's currently necessary to make code changes in edge-orders when integrating with new vendors. We have type=GOBI which routes requests to mod-gobi, but if I were to integrate with vendor FOO I'd have to update the edge-order code to route those requests to mod-foo.

Instead it would be great if we could make this configuration driven

Approach

See wiki Configuration based logic

Acceptance Criteria

• A formal schema is defined and used to validate configuration files.
• Appropriate 4xx responses are returned if a request is made for a type w/o a mapping
• unit tests are updated
• a sample mapping file is checked into git for reference - with the gobi mappings
• mappings for non-existent endpoints are ignored - a warning should be logged
• errors parsing the mappings should be logged