ManagedConnectionFactory DataSource should be lazily initialized

Currently the DataSource is initialized at component start time, however when deploying inside Tomcat users have encountered issues where the JNDI datasource is not yet available at component start time. To workaround this, we can simply make the DataSource initialization lazy and perform it on the first call to ConnectionFactory#getConnection.