CI: use latest Docker build-and-push action

This makes tagging much more complex but why not.

Signed-off-by: Paul Spooren <[email protected]>

CI: publish to testpypi

For testing only upload to the testing repository

Signed-off-by: Paul Spooren <[email protected]>

CI: publish to testpypi

For testing only upload to the testing repository

Signed-off-by: Paul Spooren <[email protected]>

api: prefer profile directly over mapped one

Within OpenWrt the profile does not always matches the `board_name`,
which is determined via device tree files. As a workaround ASU
automatically parsed the "supported" devices and mapped incomming
requests to profiles. In some rare cases (openwrt#319) the support profile is
actually a different profile than the one installed, in this case a
device that support images with and without nand storage.

To fix this, first check if a profile with the device tree model exists
(by replacing `,` with `_`) and only use the *supported mapping* if it
does not.

Fixes: openwrt#319

Signed-off-by: Paul Spooren <[email protected]>

black: apply style to tests

Signed-off-by: Paul Spooren <[email protected]>

api: add /api/v1/stats/profile_installations

Counts how many time a profile was build

Signed-off-by: Paul Spooren <[email protected]>

Merge branch 'master' of github.com:aparcar/asu

api: fixup build request example

Signed-off-by: Paul Spooren <[email protected]>

asu: switch to connexion

Using connexion allows to use OpenAPI definitions to design the API and
automatically validate parts of it. This should improve testing and
documentation at once.

Signed-off-by: Paul Spooren <[email protected]>

fixup tests for new mapping

Signed-off-by: Paul Spooren <[email protected]>