Feature/button

[finger563]

Description

• Added button component which provides a wrapper for easily adding an interrpupt-driven physical button input for which the latest state can be read or a state change event can be subscribed to
• Added example for button component
• Updated and rebuilt docs
• Updated ci

Motivation and Context

Having developed a few boards and code for managing button inputs, it seemed like a good idea to have a more reusable class for configuring and managing the button logic - especially to make use of the EventManager topics to allow the button to broadcast its state changes to multiple interested components.

How has this been tested?

Building and running the new example.

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.