Service ports hacks

These things all make me sad.

I think `ReposeInstanceInfo` might have to go away, because with the discovery of many Jettys and many servlet contexts, and that we're creating at least two Spring Contexts now (augh!), some of this stuff isn't correct any longer. If we can operate on the assumption that the system-model only creates one jetty to run under locally, rather than potentially running many localhost jettys on different ports (Why would you do this?!?!) I think we can set up the `SystemModelInterrogator` to provide the local repose node info that is needed in a couple places. I think.