add twitter collection and enrichment flows

[india-kerle]

---

Description

This PR:

• queries the twitter API for tweets in the last 7 days from a list of gambling accounts;
• enriches this data by creating a core dataframe; a core media dataframe; saves out images as .jpeg to s3 and concatenates all collected results into one core json.

I ultimately chose not to filter by geography because according to twitter documentation, only 1-2% of tweets are geotagged. We are collecting geo info so we could filter downstream in analysis if need be.

Fixes # (issue)

This should close #5 #4

Instructions for Reviewer

You can test the collect tweets flow by not running it in production:

python ds_digital_ads/pipeline/collect_tweets_flow.py run --production False

Similarly with enrich the data by:

python ds_digital_ads/pipeline/clean_tweets_flow.py run --production False

In order to test the code in this PR you need to ...

I haven't written tests for this given its more work for EDA. but to flag downstream.

Please pay special attention to ...

Checklist:

• [x] I have refactored my code out from notebooks/
• [x] I have checked the code runs
• [ ] I have tested the code
• [x] I have run pre-commit and addressed any issues not automatically fixed
• [x] I have merged any new changes from dev
• [x] I have documented the code
  • [x] Major functions have docstrings
  • [x] Appropriate information has been added to READMEs
• [x] I have explained this PR above
• [x] I have requested a code review

[cmbrennan002]

Looks good! A couple of minor comments on the code. The first script ran great! The second also ran great, to get it working I had to do a couple of things:

[ ] Change the command line to 'enrich_tweets' (I think you might have just changed the file name at some point - also needs to be adjusted in the instructions in the .py file) [ ] pip install fsspec [ ] pip install s3fs

[india-kerle]

great! thanks @cmbrennan002 - i've updated the requirements and README.md accordingly. Let's update the gambling list in a separate PR with the google ad ids as well - this should be minor.