consolidate and simplify passthroughs

[davidangb]

for discussion.

• Consolidate multiple passthrough routes into streamingPassthrough
  • I'd like to mark passthrough as deprecated; perhaps wait until we remove some more usages of it
• Consolidate multiple *ApiService route classes into a single passthrough-only class
  • Makes it easier to see routes at a glance.
  • Eventually, I suggest that all passthroughs exist in this single class, and the only routes left in other classes are non-passthroughs
• Remove unit tests for passthrough-only routes. The streamingPassthrough directive has its own unit tests, so there's not much to test here.
  • this change feels a little squirrely. Should we add back in a unit test to confirm we are routing passthroughs to the correct underlying service?

---

Have you read CONTRIBUTING.md lately? If not, do that first.

I, the developer opening this PR, do solemnly pinky swear that:

• I've followed the instructions if I've made any changes to the API, especially if they're breaking changes
• I've updated the FISMA documentation if I've made any security-related changes, including auth, encryption, or auditing

In all cases:

• Get two thumbsworth of review and PO signoff if necessary
• Verify all tests go green
• Squash and merge. Make sure your branch deletes; GitHub should do this for you.
• Test this change deployed correctly and works on dev environment after deployment

[marctalbott]

I'm a fan of this approach. Easier to add new downstream routes and non-passthrough routes are more obvious

[kevinmarete]

Nice, this simplifies things!