feat: make system tests skipable via env

[FrogTheFrog]

Description

It's annoying to have the screen blinking, so I made these kind of test skippable.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.09%. Comparing base (f7804cc) to head (f6b5c66).

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   87.09%   87.09%           
=======================================
  Files          10       10           
  Lines         620      620           
  Branches      339      339           
=======================================
  Hits          540      540           
  Misses         44       44           
  Partials       36       36           

Flag	Coverage Δ
Linux	84.37% <ø> (ø)
Windows	87.09% <ø> (ø)
macOS	51.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.