Update SA1316 to not trigger in tuple types which are part of a member's signature, if that member is an override

[bjornhellander]

Partly fixes #3781.
Handles originally reported case (overrides), but not the case of implementing an interface.

Updated to fix the issue completely.

Fixes #3781

[codecov]

Codecov Report

❌ Patch coverage is 98.91304% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.45%. Comparing base (f5843ae) to head (1e60541).
⚠️ Report is 15 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #3782    +/-   ##
========================================
  Coverage   97.44%   97.45%            
========================================
  Files         926      931     +5     
  Lines      110283   110679   +396     
  Branches     3319     3327     +8     
========================================
+ Hits       107467   107859   +392     
- Misses       1847     1850     +3     
- Partials      969      970     +1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bjornhellander]

Any comments on this, @sharwell?

[bjornhellander]

Rebased and updated to also handle members implemented from an interface, making it a complete fix for the linked issue.
Also moved a string allocation to make it not occur as often.

Ready for review.

[sharwell]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".