Arm backend Split up ZephyrOS tests per target and add SDK to docker

[zingo]

Summary

Split ZephyrOS tests per target so tests can run separate if wanted
and add support to run multipe tests after setup if you want to run
them all localy.

This removed the allowpattern as it would not stop bad code anyway
but gives the false impression that it does, removing the check also
make the code more easy to understant.

This also introduces invisible tags in the README.md in the form of

To make the parsing a bit more machine friendly and to make it easier
to change the readable text without strange test side effects.

This also only set git user in CI scripts if not already set and backup test folder so you don't destroy existing work or test data. This allows the script to be run locally more easy for testing.

Test plan

Test is part of this PR

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16868

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures

As of commit c5238d3 with merge base 4ef9b51 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest-editable / macos / macos-job (gh)
  backends/xnnpack/test/ops/test_conv2d.py::TestConv2d::test_fp16_conv2d
• trunk / test-mcu-cortex-m-backend / linux-job (gh)
  RuntimeError: Command docker exec -t 0f9b15621dbe3c0e49ae04402b13e4fddee04026c4bbf64abe748467c9cb335e /exec failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zingo]

Cortex-M fails: test_implementation_activation (12 fails) and test_implementation_linners (1 fail) are also failing on main.

[zingo]

Hi @SS-JIA or @rascani anything you want to check/look at with this ZephyrOS tests update before merging?

[rascani]

Hi @SS-JIA or @rascani anything you want to check/look at with this ZephyrOS tests update before merging?

This looks good to me. Thank you for setting this up!