Timer component: Ambigious transactional behaviour

Timer components(i.e. implementation.timer) could be made transaction by configuring Transation intent(i.e. managedTransaction).
There are 2 versions of QuartzTimerService configured in quartz.composite one for transactional and other for non-transactional.

Since we using auto-wiring, incorrect version gets wired to TimerComponentBuilder.

On my Windows machine, component is always transactional,eventhough I didn't specifiy transaction intent.

Fix is to wire QuartzTimerServices explicity in TimerComponentBuilder.