MemoryDataStore addFeatures() with FeatureReader overrides exiting Features for same type
Calling addFeatures() twice the second call overrides all exiting features. Since it's called add the expectations of users would be that implementation extends exiting collections for the same SimpleFeatureType.
Mass transitioning all resolved issues that have not been updated in the last month to closed state
addFeatures(SimpleFeatureIterator iterator) has the same problematic behavior
addFeatures(FeatureReader reader) doesn't work correctly while others were fine. Adjusted description and tests
Added test case patch that shows the behavior. addFeature() is fine whereas addFeatures() methods are not