Add screen capture functionality for TekScope device driver family

[nfelt14]

Proposed changes

feat: Added a screen capture mixin and implemented the functionality for the TekScope family of device drivers

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have followed the guidelines in the CONTRIBUTING document
• I have signed the CLA
• I have checked to ensure there aren't other open Pull Requests for the same update/change
• I have created (or updated) an Issue to track the status of this update/change and updated the link in this PR description (see above in the Proposed changes section) using the wording Addresses #<issue_number>
• I have performed a self-review of my code
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• Basic linting passes locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have added necessary documentation (if appropriate)
• I have updated the Changelog with a brief description of my changes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (dd63403) to head (f23bf24).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #342   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          159       160    +1     
  Lines         4489      4547   +58     
  Branches       784       799   +15     
=========================================
+ Hits          4489      4547   +58     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[amccann-Tek]

Couple questions:
What are your thoughts on not requiring a file name and just using the standard date time format?
And
Assuming we can trigger and take multiple events a second, are we able to increment or handle the case where there might be a duplicate file name collision?

[nfelt14]

Couple questions: What are your thoughts on not requiring a file name and just using the standard date time format? And Assuming we can trigger and take multiple events a second, are we able to increment or handle the case where there might be a duplicate file name collision?

My thoughts would be to let the user decide if they want the filename to be datetime or not, then tm_devices doesn't need to worry about name collisions, since that is out of its control.

[amccann-Tek]

Couple questions: What are your thoughts on not requiring a file name and just using the standard date time format? And Assuming we can trigger and take multiple events a second, are we able to increment or handle the case where there might be a duplicate file name collision?

My thoughts would be to let the user decide if they want the filename to be datetime or not, then tm_devices doesn't need to worry about name collisions, since that is out of its control.

For that first part I meant more along the lines of allowing
save_screenshot() to be valid, and default output would be date_time naming.

[nfelt14]

Couple questions: What are your thoughts on not requiring a file name and just using the standard date time format? And Assuming we can trigger and take multiple events a second, are we able to increment or handle the case where there might be a duplicate file name collision?

My thoughts would be to let the user decide if they want the filename to be datetime or not, then tm_devices doesn't need to worry about name collisions, since that is out of its control.

For that first part I meant more along the lines of allowing
save_screenshot() to be valid, and default output would be date_time naming.

I could add that in.

[github-actions]

Test Results (ubuntu)

path	passed	subtotal
tests/test_afgs.py	2	2
tests/test_alias_dict.py	1	1
tests/test_all_device_drivers.py	100	100
tests/test_alternative_connection_addresses.py	19	19
tests/test_awgs.py	4	4
tests/test_config_parser.py	39	39
tests/test_device_manager.py	17	17
tests/test_devices_legacy_tsp_ieee_cmds.py	3	3
tests/test_extension_mixin.py	1	1
tests/test_generate_waveform.py	6	6
tests/test_helpers.py	73	73
tests/test_ieee_scpi_cmds.py	1	1
tests/test_margin_testers.py	5	5
tests/test_pi_device.py	1	1
tests/test_psu.py	1	1
tests/test_rest_api_device.py	10	10
tests/test_scopes.py	9	9
tests/test_singleton.py	1	1
tests/test_smu.py	4	4
tests/test_ss.py	1	1
tests/test_tm_devices.py	425	425
tests/test_unsupported_device_type.py	1	1
tests/test_verification_functions.py	6	6
TOTAL	730	730

Link to workflow run

[github-actions]

Test Results (windows)

path	passed	subtotal
tests\test_afgs.py	2	2
tests\test_alias_dict.py	1	1
tests\test_all_device_drivers.py	100	100
tests\test_alternative_connection_addresses.py	19	19
tests\test_awgs.py	4	4
tests\test_config_parser.py	39	39
tests\test_device_manager.py	17	17
tests\test_devices_legacy_tsp_ieee_cmds.py	3	3
tests\test_extension_mixin.py	1	1
tests\test_generate_waveform.py	6	6
tests\test_helpers.py	73	73
tests\test_ieee_scpi_cmds.py	1	1
tests\test_margin_testers.py	5	5
tests\test_pi_device.py	1	1
tests\test_psu.py	1	1
tests\test_rest_api_device.py	10	10
tests\test_scopes.py	9	9
tests\test_singleton.py	1	1
tests\test_smu.py	4	4
tests\test_ss.py	1	1
tests\test_tm_devices.py	425	425
tests\test_unsupported_device_type.py	1	1
tests\test_verification_functions.py	6	6
TOTAL	730	730

Link to workflow run

[github-actions]

Test Results (macos)

path	passed	subtotal
tests/test_afgs.py	2	2
tests/test_alias_dict.py	1	1
tests/test_all_device_drivers.py	100	100
tests/test_alternative_connection_addresses.py	19	19
tests/test_awgs.py	4	4
tests/test_config_parser.py	39	39
tests/test_device_manager.py	17	17
tests/test_devices_legacy_tsp_ieee_cmds.py	3	3
tests/test_extension_mixin.py	1	1
tests/test_generate_waveform.py	6	6
tests/test_helpers.py	73	73
tests/test_ieee_scpi_cmds.py	1	1
tests/test_margin_testers.py	5	5
tests/test_pi_device.py	1	1
tests/test_psu.py	1	1
tests/test_rest_api_device.py	10	10
tests/test_scopes.py	9	9
tests/test_singleton.py	1	1
tests/test_smu.py	4	4
tests/test_ss.py	1	1
tests/test_tm_devices.py	425	425
tests/test_unsupported_device_type.py	1	1
tests/test_verification_functions.py	6	6
TOTAL	730	730

Link to workflow run