chore: update sidebar highlights for docs

Author: github-actions[bot]

developer-guide/09-Storage and the filesystem/02-filesystem.md

@@ -2,7 +2,6 @@
 title: Important locations on the filesystem
 slug: /filesystem-locations
 hide_table_of_contents: true
-sidebar_class_name: sidebar-item--updated
 ---
 
 # Important Raspberry Pi Locations for Pioreactor Images

developer-guide/10-Hardware/10-custom-hardware.md

@@ -3,7 +3,6 @@ title: Customize the hardware interface
 slug: /custom-hardware
 description: Extend or override Pioreactor hardware definitions by layering YAML files that hardware.py reads.
 hide_table_of_contents: true
-sidebar_class_name: sidebar-item--updated
 ---
 
 Pioreactor's hardware layer is intentionally data-driven. Everything in [`core/pioreactor/hardware.py`](https://github.com/pioreactor/pioreactor/blob/main/core/pioreactor/hardware.py) loads user-editable YAML files from `~/.pioreactor/hardware/` (or the folder pointed to by the `DOT_PIOREACTOR` env var). By editing these files you can rewire pins, add new peripherals, or describe an entirely new bioreactor model without touching the Python code. Pair these configs with [custom bioreactor model definitions](/developer-guide/custom-bioreactor-models) so the UI, safety limits, and wiring stay in sync.

developer-guide/10-Hardware/11-custom_models.md

@@ -2,7 +2,6 @@
 title: Custom bioreactor models
 slug: /custom-bioreactor-models
 hide_table_of_contents: true
-sidebar_class_name: sidebar-item--updated
 ---
 
 :::tip

user-guide/03-Extending your Pioreactor/01-cluster-management/03-backup-and-restore-system-files.md

@@ -4,7 +4,6 @@ title: Back up and restore Pioreactor system files
 slug: /backup-system-files
 description: Export and import a Pioreactor’s ~/.pioreactor directory from the Inventory page.
 hide_table_of_contents: true
-sidebar_class_name: sidebar-item--updated
 ---
 
 Each Pioreactor keeps its configuration, calibration data, and persistent state inside `~/.pioreactor`. The Inventory page now lets you export that directory as a system archive (`.zip`) for safekeeping and import it onto the same unit when you need to restore or clone a setup.