property preparsing POC

this pr contains some work i have been doing to better support the various places where properties and substitutions can occur in a JSR job. previously properties were only being resolved via a factory post processor, iterating through bean properties. this won't work in all cases, for example when obtaining a value from an xml element in a parser and storing it in for example an arbitrary data structure, resulting in unresolved property operator strings being passed around.

rather than resolving properties via the post processor, this change introduces a hook into the preprocessing of the XML to transform the document with the expected property replacements since we have them prior to loading the context. this occurs just prior to loading bean defintions.

the intended end result is the transformed document is well formed, with all applicable properties replaced with their expected values and ready to be loaded into the context.

this PR does not make any new TCK tests pass, it just contributes to revealing the next issues.