Feat/monitor data status

[anngvu]

Close #75.

Based on that initial bot suggestion, which was a good start but needed these revisions after analysis and/or testing:

Script:

• Use auth token correctly
• More efficient query where server can do most of the work/pull less data
• Should not use query for annotations of experimentData because files can be uploaded but not annotated --
  for this, it doesn't matter if files are annotated, really just need to check if data files exist in the project.
• Filter out Data Sharing Plans via creator heuristics.
• Add syn.get, revise syn.store syntax
• Add CLI flags
• Add tests

Workflow:

• Write to be run in service catalog, add Dockerfile.

[allaway]

LGTM - I had one suggestion but it's not a blocker for merging!

[allaway]

Suggested change

	fileview_df = syn.tableQuery(f"SELECT projectId,count(*) as N FROM {FILE_VIEW_ID} WHERE type='file' and createdBy not in ('3421893', '3459953', '3434950', '3342573') and projectId in {QUERY_IDS} group by projectId").asDataFrame()
	fileview_df = syn.tableQuery(f"SELECT projectId,count(*) as N FROM {FILE_VIEW_ID} WHERE type='file' and createdBy not in ('3421893', '3459953', '3434950', '3342573') and projectId in {QUERY_IDS} group by projectId").asDataFrame()

Should we maintain a table on the portal backend project to keep the createdBy principal ids in? Then we could also use that table for reporting (instead of the one listed in the readme here https://github.com/nf-osi/internal-reports)

[anngvu]

Yeah, we probably need to start a table as a source of truth for who should be excluded for these sorts of things. I think we can do that first and then go back to revise these two + others.