chore(python): Enable --strict-markers in all pytest configurations

[SyntaxColoring]

Overview

While working on RLAB-256, I got confused by a silly mistake where I misspelled a pytest mark, like pytest.mark.ot3only instead of pytest.mark.ot3_only.

It turns out that there's an option to prevent this, --strict-markers, and it's easy to enable in all of our Python projects. This PR does that.

Test Plan

Make sure CI keeps passing.

Review requests

Is there any reason not to do this?

Risk assessment

No risk.

[codecov]

Codecov Report

Merging #12596 (c285395) into edge (bb34bd7) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             edge   #12596      +/-   ##
==========================================
- Coverage   73.59%   73.57%   -0.03%     
==========================================
  Files        2267     2267              
  Lines       62341    62370      +29     
  Branches     6592     6602      +10     
==========================================
+ Hits        45881    45886       +5     
- Misses      14886    14910      +24     
  Partials     1574     1574              

Flag	Coverage Δ
app	72.10% <ø> (-0.13%)	⬇️
g-code-testing	96.44% <ø> (-0.08%)	⬇️
hardware	58.66% <ø> (+<0.01%)	⬆️
notify-server	89.13% <ø> (ø)
protocol-designer	46.34% <ø> (ø)
shared-data	75.35% <ø> (ø)
step-generation	88.20% <ø> (ø)
system-server	96.07% <ø> (ø)
update-server	65.65% <ø> (ø)
usb-bridge	81.35% <ø> (ø)

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

see 5 files with indirect coverage changes

[SyntaxColoring]

I'll be out until May 4. If this gets an approval from someone, feel free to merge it in my absence.

[sfoster1]

lgtm