fix: using eeprom.update() instead of eeprom.write() ; saves potentia…

[labamichnetvoll]

This pull request is using EEPROM.update() instead of EEPROM.write()

This change can save writing cycles to the EEPROM.

this is better because of:

Note: An EEPROM write takes 3.3 ms to complete. The EEPROM memory has a specified life of 100,000 write/erase cycles, so using this function instead of write() can save cycles if the written data does not change often

EEPROM Library -> update

[Copilot]

Pull Request Overview

This pull request improves EEPROM usage by replacing EEPROM.write() calls with EEPROM.update() to extend the EEPROM's lifespan by only writing when values actually change.

• Replaces all EEPROM.write() calls with EEPROM.update() throughout the codebase
• Preserves existing functionality while reducing unnecessary write cycles
• Applies the optimization to configuration settings, state management, and user preference storage

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The setMainColor function still uses EEPROM.put() instead of EEPROM.update(). For consistency with this PR's goal of optimizing EEPROM writes, consider updating setMainColor to use EEPROM.update() as well.

[labamichnetvoll]

The PR actually looks unnecessary, since the library used already contains a built-in check.
this library doesn't use the EEPROM.update() function for this

Sorry for the ping