Multiple UdigTransaction seen in the wild

This one is preventing development and debugging of our ArcSDE support. We can step through in the debugger and see:

• the ArcSDE FeatureSource (used by the renderer) use one UdigTransaction; while
• the ArcSDE FeatureStore (used by edit tools) use another UdigTransaction!

I am going to apply the following hack to BasicFeatureRenderer in order to mask this problem; long term solution needed:

		FeatureSource featureSource;
		featureSource = layer.getResource(
				FeatureStore.class, new SubProgressMonitor(monitor, 0));
		if( featureSource == null ){
		    featureSource = layer.getResource(
	                FeatureSource.class, new SubProgressMonitor(monitor, 0));
		}

The above code forces the renderer to try asking for a FeatureStore first, this should not be needed it is a HACK and can be removed when we have verified that the "interceptors" are only making a single UdigTransaction.