getMovebankData doesn't account for all outlier-related event attributes
Problem: Currently getMovebankData will include points with import-marked-outlier=T and exclude points with manually-marked-valid=T.
Solution: I recommend updating getMovebankData to use "visible" rather than specific outlier columns to identify which records to include by default when accessing data. This is accessible by API, e.g. with https://www.movebank.org/movebank/service/direct-read?entity_type=event&study_id=2911040&attributes=individual_id,timestamp,location_long,location_lat,visible
Background: For a long time we only had algorithm-marked-outlier and manually-marked-outlier, so looking at these was fine. We've since added import-marked-outlier for data feeds whose providers pre-filter the results according to their own procedure, and manually-marked-valid to override filter results when needed. The attribute "visible" aggregates the results of all outlier-related attributes, and is what we use to display tracks on the Movebank map. So switching to this would eliminate the need to update again later if other outlier attributes are added.