Research avoiding multiple alias resolutions for the same abstract service

[cspray]

It is possible that an abstract service is attempted to have its alias resolved that results in no alias resolutions. We should see if we can skip future checks for similar services since we know the resolution won't succeed. This happens because there are a list of AliasDefinition instances that could list the abstract service multiple times.

[cspray]

This could potentially have some value. We'd be saving iterating over service definitions needlessly during a part of the process that has not been optimized, relative to static analysis where caching drastically increases performance. However, it would involve adding and keeping up with state in the StandardAliasDefinitionResolver. Since this is a fairly low priority item I'm going to wait until, or if, more users could also see value out of doing this.

Will move this into the 2.x milestone.