Handle indirect changes comparison in net new files

[suejung-sentry]

Describe the bug
I believe when we try to fetch segments data in the Indirect changes comparison against a file that exists in main but not yet in the branch for the PR, there is an "unknown path" error.

To Reproduce
Here are a couple examples - go to the links and try to expand the toggle and see the page resolve to an error page.
https://app.codecov.io/github/codecov/codecov-api/pull/945/indirect-changes
https://app.codecov.io/github/codecov/gazebo/pull/3457/indirect-changes

The ImpactedFileComparison query to fetch segments shows UnknownPath error. From what I can tell, this appears to happen in the case when the PR needs to get rebased to pick up information about a new file.

Example

• https://app.codecov.io/github/codecov/codecov-api/pull/945/indirect-changes
• where the core/management/commands/delete_rate_limit_keys.py "missing file" was added - https://github.com/codecov/codecov-api/pull/935/files a couple commits up in main
• but the PR related to the "broken page", doesn't know about this file yet - [launchweek demo] Add Sentiment class  codecov-api#945
• here's the GCS coverage report in case helpful - https://console.cloud.google.com/storage/browser/_details/codecov/v4/repos/EB9CABCCED3D6785D21E028F277F3018/commits/fa4ca76eab9065ce1e6bdd893cbb3951a0d5df76/json_data/commits/report_json/fa4ca76eab9065ce1e6bdd893cbb3951a0d5df76.json;tab=live_object?project=genuine-polymer-165712

To fix, confirm that is what's going on here and have a better comparison for this case (or a better error message)

Additional context

hangs around with loading spinner for a bit, then resolves to the error page due to the UnknownPath

[eliatcodecov]

@katia-sentry , based on the discussion above, it feels like @suejung-sentry has the most context. But I'll leave assignment to you since I don't have a sense of difficulty on this ticket nor the upcoming sprint schedule of the team.

[suejung-sentry]

Closing this ticket as the issue described here should be resolved when the work in #2803 is done