FEAT: Identify coupling 5649

[amichel0205]

Description

This feature is useful for large RF board where user want to identified unwanted coupling.
User will specify:

Sparameter file full path
Log file full path
low_loss and high_loss range
Frequency start at which to start looking for the coupling(such we can skip low frequency where DC block exist)
Sample frequency(to speed up process chack coupling at each sample)

Issue linked

Close #5649

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate tests (unit, integration, system).
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved by the PR if any.
• I have agreed with the Contributor License Agreement (CLA).

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[codecov]

Codecov Report

Attention: Patch coverage is 86.11111% with 5 lines in your changes missing coverage. Please review.

Project coverage is 85.21%. Comparing base (8214b24) to head (6410a3d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5659   +/-   ##
=======================================
  Coverage   85.20%   85.21%           
=======================================
  Files         156      156           
  Lines       61071    61107   +36     
=======================================
+ Hits        52035    52070   +35     
- Misses       9036     9037    +1     

[hui-zhou-a]

@amichel0205 please use a valid s-parameter for testing.

[Samuelopez-ansys]

LGTM

[SMoraisAnsys]

I left some refactoring proposition.

[hui-zhou-a]

LGTM

Requested changes implemented