CODEOWNERS auto-assignment not working for Gitlab integration with custom domain

[serglom21]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

(Filing on behalf of a customer with a open customer case)
Trying to set up a Gitlab Integration with a custom instance domain like namespace.example.com seems to break features like auto-assignment based on CODEOWNERS and Suspect Commits for iOS and Android. There may be some quirks when it comes to reading the absolute path from the stack trace from these type of domains

Expected Result

I would expect CODEOWNERS based assignment and Suspect Commits to work as it works for regular domains

Actual Result

Suspect Commits do not show up on issue details view and CODEOWNERS based assignment does not work even though the path of the frames match the rules defined in the file

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[mrduncan]

We're planning on taking on this work as a part of our core product rotation this quarter.