feat(open-pr-comments): get sentry projects and filenames

[cathteng]

Reverse code map filenames from Github (source_root) to filenames as stored in Sentry (stack_root). Also fetch the projects associated with these code mappings.

For ER-1807

[codecov]

Codecov Report

Merging #59952 (609597b) into master (301ebf6) will increase coverage by 0.00%.
Report is 13 commits behind head on master.
The diff coverage is 94.73%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #59952   +/-   ##
=======================================
  Coverage   80.76%   80.76%           
=======================================
  Files        5179     5179           
  Lines      227391   227401   +10     
  Branches    38253    38255    +2     
=======================================
+ Hits       183654   183663    +9     
  Misses      38145    38145           
- Partials     5592     5593    +1     

Files	Coverage Δ
...lease_thresholds/release_threshold_status_index.py	83.87% <100.00%> (-0.21%)	⬇️
src/sentry/tasks/sentry_apps.py	85.29% <100.00%> (ø)
static/app/utils/releases/releasesProvider.tsx	72.97% <ø> (-0.72%)	⬇️
...entry/tasks/integrations/github/open_pr_comment.py	98.07% <93.33%> (-1.93%)	⬇️

... and 2 files with indirect coverage changes

[nhsiehgit]

just comment on the raw sql 🤔

Can we chat w/ maybe @wedamija or someone and see if there's any better alternative?

[cathteng]

StrIndex returns the index in which there is a match, but uses 1-indexing. it returns 0 if there is no match

[vartec]

Q: is this case-sensitive?

[cathteng]

i'm assuming it works like regular string indexing, but i can check

[vartec]

Apparently it depends on the DB backend used. In our case it's PostgreSQL, where it's rendered as STRPOS(), which is indeed case-sensitive.