Replace box-emu-hal (non-component) with actual box-emu component and use esp-box component from espp

[finger563]

Description

• Remove box-emu-hal component which was just a collection of static functions in a namespace (and not very well designed)
• Update espp submodule to have newest EspBox component which automatically detects and configures touch, display, and audio for both ESP32-S3-BOX and ESP32-S3-BOX-3 - no longer requiring a recompile / menuconfig to select box version! 🎉
• Add new box-emu component which leverages EspBox component and provides a nicer interface
• Update sd card configuration to use 16k allocation unit size for better performance instead of the default 512b.

Motivation and Context

Related espp PR: esp-cpp/espp#264

This PR enables the box-emu code to run on all versions of the box-emu as well as all versions of the esp-box, without needing to recompile. Previously, you would have to recompile if you wanted to target different versions of the esp-box (but not if you wanted to target different versions of the box-emu).

Finally, this helps clean up the code and remove code that's a little more esp-box related, now that it has an actual component class for the BoxEmu and it uses the espp::EspBox component as well.

Additionally, this code also speeds up file access by increasing the allocation unit size configured for the sd card.

How has this been tested?

• Building and running box-emu/example on Box-3 (V1)
• Building and running box-emu/example on Box (V1)
• Building and running box-emu/example on Box (V0)

Building and running main on Box-3 (V1) and testing all the emulators :)

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

Box-3 V1:

Box V1:

Box V0:

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! ✅