* update lib index during update

* Apply suggestions from code review

Co-authored-by: Davide <[email protected]>

---------

Co-authored-by: Luca Rinaldi <[email protected]>
Co-authored-by: Davide <[email protected]>

* fix(pkg/board/remote): adb kill all port use wrong command

* add adb forward test

* embed the script in then dockerfile

* Revert "embed the script in then dockerfile"

This reverts commit b7481d3.

* feat: add bridge monitor command

* Update internal/monitor/monitor.go

Co-authored-by: Cristian Maglie <[email protected]>

* improve description

* apply code review suggestions

* propertly implement the internal function

* handle also text type

* Update internal/monitor/monitor.go

Co-authored-by: Davide <[email protected]>

* Update internal/monitor/monitor.go

Co-authored-by: Davide <[email protected]>

* Update internal/monitor/monitor.go

Co-authored-by: Davide <[email protected]>

* add monitor test

* fixup! add monitor test

* fixup! fixup! add monitor test

* fixup! fixup! fixup! add monitor test

* fixup! fixup! fixup! fixup! add monitor test

---------

Co-authored-by: Cristian Maglie <[email protected]>
Co-authored-by: Davide <[email protected]>

* Updates to libraries-api.

Now some libraries may be tagged as dependencies, and also be
automatically removed if no more needed.

* Forget parameter in ProfileLibRemove... oops

* fix: missing version on SketchLibraryRemove call

* Updated arduino-cli patch

* Updated CLI implementation

* Updated Arduino CLI to 1.4.0

…late (#136)

When a new App is generated, it contains a sketch with a sketch project file that defines a build profile . Previously,
the `fqbn` key ofthis build profile was set to `arduino:zephyr:unoq`. Since the build profile is indeed used to control
the dependencies of the sketch, the user would be led to also believe that the FQBN specified in the build profile is
used when compiling and uploading the sketch. This is not so. An FQBN is instead hardcoded into the compilation and
upload code, meaning the `fqbn` key in the build profile has absolutely no effect.

The obvious problem with this is that it will lead the advanced user to believe they can configure the FQBN used by App
Lab via the `fqbn` key of the build profile. For example, they might wish to use the
`arduino:zephyr:unoq:flash_mode=flash,wait_linux_boot=no` FQBN in cases where the sketch code is not reliant on the
immediate availability of the Linux machine and they do not wish for the execution of the sketch program to be delayed
after power on.

Even more confusing is the fact that the `arduino:zephyr:unoq:flash_mode=ram` FQBN used when uploading is different from
the FQBN the default build profile would lead the user to believe is in use (since the default value of the `flash_mode`
custom board option is `flash` NOT `ram`, and thus the `arduino:zephyr:unoq` used in the template is equivalent to
`arduino:zephyr:unoq:flash_mode=flash`).

Removing the unused and misleading `fqbn` key from the generated build profile will better communicate the actual
situation to the user.

* initial flasher import

* implement getOSImageVersion

* refactoring

* refactoring

* code review fix

* refactoring test

* remove unused parameter

* enhance tests

* move os_image funcs into new file

* remove log

* code review fix

* Bump runner version to 0.6.2 and remove 0.6.1 assets and examples

* Update brick details test to handle hidden variables correctly

* Remove expected config variables and variables from tests

* fix(update): always try to restart the app-cli daemon

* Update internal/update/apt/service.go

Co-authored-by: Alby <[email protected]>

---------

Co-authored-by: Alby <[email protected]>