Use of classpath*: / Windows

[Cantor, Scott]

> It's all  fairly undocumented/unsupported to override any of this
> functionality, which I guess is what we knew. Apart from research I'm not
> tremendously optimistic that it's worth the time to try and correct as long as
> we're careful where we actually support the use of classpath*

Logged my findings in IDP-753. TL;DR, it's basically down to overriding/hijacking a factory bean to replace a built-in class or two with some custom versions, which I'm sure we could manage if we think it's warranted.

The bean isn't all that logic-heavy per se, so likely not a big maintenance burden and it's not like SWF is pumping out releases.

But still an open question as to the value given that we've managed to make one registry work with user-supplied flows and could probably support auto-injection of plugin flows now if the classpath* syntax were used for just that property, and carefully avoided otherwise.

-- Scott