Fix for the long-standing issue: UnsafeThirdPartyFunctionCall was marking internal extension functions for third-party types as third-party functions, which is wrong. This PR fixes that by checking the declaration package for the function in addition to its container.
Review checklist (to be filled by reviewers)
[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
What does this PR do?
Fix for the long-standing issue:
UnsafeThirdPartyFunctionCall
was marking internal extension functions for third-party types as third-party functions, which is wrong. This PR fixes that by checking the declaration package for the function in addition to its container.Review checklist (to be filled by reviewers)