* feat: update examples to 0.5.1

* fixup! feat: update examples to 0.5.1

* fix(pkg/board): handle adb connection error

* add a warning

* don't expose the function

* rename errors

* fixup! rename errors

* fixup! don't expose the function

* implement code review suggestions

* nit

* remove models field from brick list

* add lite model information to brickDetails endpoint

* fix test

* fix test end2end

* refactoring

* rename struct

* fix tests

* add unit test for brick details

* add compatible models in brickinstance details

* fix test e2e

* fix test e2e

* add unit tests

* fix tests

* remove omitempty from field compatible_modules

* update field name for brick details endpoint

)

* feat(tests): add bricks index test and YAML data for bricks

* refactor: rename index generation functions to Load for consistency

* use paths.path as argument in app.load

* use dir instead of path in app.Load
---------

Co-authored-by: Luca Rinaldi <l.rinaldi@arduino.cc>

* brick - add require on list and details

* require_model for the app bricks

* fixing yaml ser

* list app brick detalis

* add tests on reqmodel

* rename to RequireModel

* TestBricksList test

* TestAppBrickInstanceDetails

* fix

* update tests

* add RequireModel to test

* add test IC

* remove models

* Update internal/orchestrator/bricksindex/testdata/bricks-list.yaml

Co-authored-by: Davide <davideneri18@gmail.com>

* Update internal/orchestrator/bricksindex/testdata/bricks-list.yaml

Co-authored-by: Davide <davideneri18@gmail.com>

* Update internal/orchestrator/bricks/testdata/bricks-list.yaml

Co-authored-by: Davide <davideneri18@gmail.com>

* revert

---------

Co-authored-by: Davide <davideneri18@gmail.com>

When a new App is created, it is populated with a simple Python script and "bare minimum" Arduino sketch.

For initial explorations of a new system, or when troubleshooting, it is common to create very simple programs (AKA
"Hello, world!"). Although a complex App will typically consist of a Python script and Arduino sketch program working in
coordination, for users with prior experience with Arduino the natural approach to creating a minimal App will be to
simply write some familiar Arduino sketch code, leaving the default Python script code as-is.

The App is considered to be in a "stopped" state as soon as the Python script exits. This is the correct approach, but
may be confusing to users due to the fact that, except perhaps under exceptional conditions, the Arduino sketch program
runs perpetually. The author of a minimal sketch-based "Hello, world!" App will find it unintuitive if their App goes
into a "stopped" state immediately after starting. The previous default Python script produced exactly that result.

The default Python script is hereby changed to the more intuitive behavior of running perpetually.

Co-authored-by: Davide <davideneri18@gmail.com>

* remove compatible models from brick instance list endpoint

* add unit and e2e test