feat(base_component): add new base component and improve I2C class + example

[finger563]

Description

• Add base component which contains logger with some methods for setting logging level and tag for the logger
• Update i2c to subclass base component and add some extra methods for writing / reading with std::vector. Also added some logging to the i2c component
• Add i2c format helpers for logging the i2c bus which is initialized
• Add missing i2c destructor
• Update i2c example to test new i2c destructor
• Add i2c menu to i2c example for allowing interactive control / query of the i2c bus using cli component
• Update i2c and cli component to have s3 defualts file configuring the console output port to be usb serial/jtag
• Update components (non-peripherals) to subclass espp::BaseComponent
  • adc
  • bldc_driver
  • bldc_haptics
  • bldc_motor
  • button
  • controller
  • display
  • encoder
  • event_manager
  • file_system
  • ftp
  • i2c
  • input_drivers
  • joystick
  • led
  • led_strip
  • monitor
  • pid
  • rmt
  • rtsp
  • socket
  • task
  • thermistor
  • timer
  • wifi

Motivation and Context

A base component reduces boilerplate by adding logger and some log related functions to the base class.

How has this been tested?

• Building and running the new i2c example.
• Building and running the task example
• Building and running the adc example
• Building all the examples using CI (in this PR)

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