Feature/metadata modification tracking

[finger563]

Description

• Update gui to keep track of the last time the metadata file was modified, and only reload the rom list if it has been modified since we loaded it last (e.g. if USB MSC was enabled and it was updated). Keeps the gui from hanging when going from settings page to rom list if the rom list did not need to be regenerated
• Set default video setting to be FIT since it keeps aspect ratio while maximizing the screen utilization
• Increased LVGL heap size from 50k to 60k to support additional roms in the rom list

Motivation and Context

Previously, any time you left the settings page to go back to the rom list, it would re-read the metadata file and fully recreate the rom list from scratch, which can take a second or so. This was not a good user experience - esp. if the rom list did not change.

This PR makes the gui track the last modified time of the metadata file, and only if the last modified time is not the same as what we saw last, then we will update the rom list.

How has this been tested?

Building and running on ESP32-S3-BOX with hardware V0 and V1.

Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):

Types of changes

• 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)
• Documentation Update
• Hardware (schematic, board, system design) change
• Software change

Checklist:

• My change requires a change to the documentation.
• I have added / updated the documentation related to this change via either README or WIKI

Software

• I have added tests to cover my changes.
• I have updated the .github/workflows/build.yml file to add my new test to the automated cloud build github action.
• All new and existing tests passed.
• My code follows the code style of this project.

[github-actions]

✅Static analysis result - no issues found! ✅