If 'use_backup' option is set to True in config.py, the bot collects
a backup of the stats, so in case of unexpected termination the bot
can continue the test series from the test case where it was interrupted.

hid_gpio is a mynewt based, DIY active hub
https://github.com/kasjer/hid_gpio

Since autopts bot is able to continue testing after an interruption,
let's add a timeguard to cron that will detect whether a test cases run
smoothly.

Make reports generation more generic.

Adding back the test profiles mbtm and dfum to workspace with default IXIT
values.

Signed-off-by: m-alperen-sener <alperen.sener@nordicsemi.no>

- With TCRL-2024-1 profiles MBT and DFU changed to MBTM and DFUM
respectively. Updating the test case names and profile names.
- TSPX_Reception_Counter and TSPX_Server_Timeout removed and separate
TSPX_Client_Timeout_Base and TSPX_Server_Timeout_Base added for client
and server.
- Adding missing DFUM tests to zephyr iut_config.
- Adjust the CONFIG_BT_MESH_BLOB_BLOCK_SIZE_MIN/MAX according to MBTM
test cases.
- Increase the CONFIG_BT_MESH_SETTINGS_WORKQ_STACK_SIZE to 1200 instead
of default 800.

Signed-off-by: m-alperen-sener <alperen.sener@nordicsemi.no>

It is sufficient to use only prefixes of the test groups for filtering.

Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>

It happened that the TCP/IP socket of the server got stuck, so
lets restart the process at each cron job.

So far GATT service was used to create DIS but we should use one from
Zephyr.

New TCRL added more tests for CIS connnection in QoS Configured state.

Add L2CAP test case to mynewt errata list

Add missing module to client and server requirements.txt

This will enable to run specified amount of test cases from among prefixes
that are used with magic tag.

The loaded tc stats were not inited with tc database, hence
regressions could not be caught if the autopts bot was restarted
in the meantime.

Unhandled exception terminated a github cron thread.

Rarely, but it happens that restart of the testing setup fails,
e.g. because of some TCP/IP socket. Let's try restart the bot setup
again if bot terminated unexpectedly.

Remove stale ones, add newt test case.

If the requested test case prefixes were not found in cached list of
test cases, the test_cases list was empty and autopts bot
was triggered to run all test cases from PTS workspace.

GMCS was set according to test plan.

GTBS tests are now part of TBS profile.

GMCS testa are now part of MCS profile.

Adding gap_pair in wid_142 fixes various GATT/CL testcases. It may be
that PTS used to (before some update) initiate pairing procedure which
is why no btp command was used in this handler.

Fixes issue 1227.

A .py file loaded as a module is cached until it is explicitly removed
from sys.modules. So subsequent attempts to load the file only return
a reference to the existing module-dictionary. So we need to deep-copy
a config.py to prevent overwriting its original values and reuse it
e.g. in subsequent PR jobs.

This commit implements project name field into report email body.

This enabled few missing features in GAP, GATT and LE Audio profiles.

nRF54H20 SoC device added

Adds the nRF5340 audio devkit board, with capabilities to build both
application and network cores with configurable separate builds.

Each call to run_test_cases created a separate session folder. Bot enters
this function after each rebuild and flash, so many of these folders were
created, making it difficult to find logs of a specific test case.

In backup mode, these files have to be moved/deleted to start fresh
bot start. Cron does this automatically, but without the cron, one had
to do it manually.

If a test case triggered cron timeout and bot restart at its first
attempt, its result was missing in stats.

If the autopts bot was pulling logs from server longer than configured
cron timeout, cron restarted the bot in the middle. Because stats were
not saved after downloading the test case description from PTS, after
restarting the bot, it did not have them available when creating a report.

If someone would like to use a different controller and make the bot to
build/flash only appcore of nrf53 board, all they need to do from now
is to set this option "board": "nrf53_appcore" in the bot's config.py file.

CAP WIDs are using MICP and VCP commands and thus shall initialize
required BTP services.

Currently there is no way to access included service handle in Nimble
with find included services procedure. We still can use other values
that we have access to, to compare them with values from MMI which
should be enough to pass test GATT/CL/GAD/BV-03-C.