feat(framework-core): support inline multiline comments suggestions on pull requests

[TomKristie]

Framework-core logic for creating a multi-line inline comments suggesting code to a pull request given the pull request number, and the old and new contents of files that belong to the pull request.

Specifically given the input of the PR number, and a subset of the PRs files old and new file contents:

Generate the diff range between the old and new contents for each file provided by the user. This is each potential file's potential multiline comments domain. And then from the potential suggestions, create in-scope suggestions by:
Filtering out-of-scope suggestions by:
a. Filter out the files who are not in the PR (creating in-scope files)
b. Filter out the non-filtered file's lines that are out of scope of the PR (creating in-scope files with in-scope lines), and
c. Filter out the files who were too large to load the diff since the file is too large to comment on (this is tentative to change)
Take the in-scope suggestion ranges for each file and get the corresponding text.
on the PR number, make the in-scope suggestions.
Comment on what could not be commented on and why.
The remaining result is a diff range for files and file lines that are in-scope of the pull request.

Framework-core
Towards #59

[codecov]

Codecov Report

Merging #105 into master will increase coverage by 6.61%.
The diff coverage is 99.80%.

@@            Coverage Diff             @@
##           master     #105      +/-   ##
==========================================
+ Coverage   85.28%   91.89%   +6.61%     
==========================================
  Files          14       25      +11     
  Lines        1257     2295    +1038     
  Branches       87      182      +95     
==========================================
+ Hits         1072     2109    +1037     
- Misses        184      185       +1     
  Partials        1        1              

Impacted Files	Coverage Δ
src/github-handler/index.ts	94.73% <93.33%> (+19.73%)	⬆️
...ler/make-review-handler/upload-comments-handler.ts	99.20% <99.20%> (ø)
src/default-options-handler.ts	100.00% <100.00%> (ø)
...et-hunk-scope-handler/github-patch-text-handler.ts	100.00% <100.00%> (ø)
...er/comment-handler/get-hunk-scope-handler/index.ts	100.00% <100.00%> (ø)
...-hunk-scope-handler/remote-patch-ranges-handler.ts	100.00% <100.00%> (ø)
src/github-handler/comment-handler/index.ts	100.00% <100.00%> (ø)
...ndler/comment-handler/make-review-handler/index.ts	100.00% <100.00%> (ø)
...ent-handler/make-review-handler/message-handler.ts	100.00% <100.00%> (ø)
...handler/raw-patch-handler/hunk-to-patch-handler.ts	100.00% <100.00%> (ø)
... and 16 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c61da3e...1795930. Read the comment docs.

[chingor13]

Looks like we're missing some test coverage on the main comment/reviewPullRequest logic.

[chingor13]

This is looking really close!

[chingor13]

Feature request: pipe an option to make this 'REQUEST_CHANGES' or 'COMMENT'. This way someone could configure it to be a blocking review.

[TomKristie]

Wow very exciting! I don't have permissions to merge so that is up to you @chingor13 or @bcoe . Thanks for your help all along this pr. 😄