Added test org.hibernate.test.instrument.runtime.AbstractTransformingClassLoaderInstrumentTestCase#testEagerFetchLazyToOne -> org.hibernate.test.instrument.cases.TestFetchingLazyToOneExecutable.

Ultimately, the problem is that the FK column for the lazy to-one is not rendered into the select clause of the query even though the association is expected to be there due to the fetch. The to-ones here are a deviation in a way from the way the rest of the bytecode lazy attributes are handled. Normally the expectation is to utilize the `fetch all properties` phrase in the query to indicate those lazy attributes should be fetched. However, a dynamic join fetch should trigger this for lazy to-ones. In many ways this again brings up the discussion of having more than one group for bytecode lazy initialization. At the moment it is expected that all of them are initialized together.

For some reason (that I am still investigating), using `fetch all properties` works inconsistently in these cases.