feat(hid-rp): Update Gamepad Implementation

[finger563]

Description

• Update Gamepad implementation to have cleaner / easier to read report descriptor
• Update gamepad implementation to remove application collection, so that it can be used alongside other reports
• Added GamepadLedOutputReport as an example output report for handling Gamepad LEDs
• Updated hid-rp and hid-service exmaple to use new interfaces and class names for gamepad (input and leds) and to shwo use of combining multiple reports together into an application collection
• Minor updates to configuration for gamepad input report examples to work on both iOS and Android (ensuring the size of the report matches the expected size from the descriptor - no extra padding bytes at the end)
• Add includes for battery_system, consumer, generic_device, leds, and physical_input_device so they are more easily accessible to other code
• Update logging of example to make it clearer what is happening and make it easier to debug / validate.

Motivation and Context

• Improves quality and accuracy of example gamepad implementations
• Shows example for output report
• Shows example for combining input and output reports into an application
• Improves compatibility across platforms (iOS and Android)

How has this been tested?

• Building and running the hid-rp example on QtPy ESP32S3
• Building and running the hid_service example on QtPy ESP32S3 and pairing / connecting it to iOS and Android.

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

HID-RP Example:

HID Service Example:

iOS:

hid_service_ios_compressed.mp4

Android:

hid_service_android_compressed.mp4

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