Simplifying InlineConstraints tests

Right now these use a commandline adapter to inject some data into the
tests, but it's really not needed. Instead, these routes use a prefix to
ensure that the scenario under test is isolated.
why initialize this field twice?  using two statements is fine.  repeating the `CreateServices()` call is not.  more readable to execute these two statements in the constructor and revert changes to the field declaration.