Arm backend: Make upstream testing more target specific

[Michiel-Olieslagers]

This patch splits up our upstream testing such that only relevant items are installed and only required things are tested upstream. It removes any duplicate testing and makes the upstream testing structure more transparent and readable.

Change-Id: I14cf329eed03d9859aef97204a9f12185b9533a2

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 7bb11ee with merge base d4ce813 ():

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Timeout waiting for emulator to boot.

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

[meta-codesync]

@metascroy has imported this pull request. If you are a Meta employee, you can view this in D88086613.

[metascroy]

These changes look fine to me, but we're currently having issues running any CI in PyTorch due to #16017

[zingo]

@metascroy CI seen to be fixed now and I rebased to retrigget job, now Meta internal and rebased version differ and we need help to re-import, hope that is OK

[metascroy]

@metascroy CI seen to be fixed now and I rebased to retrigget job, now Meta internal and rebased version differ and we need help to re-import, hope that is OK

Re-imported

[zingo]

Oh no :( @Michiel-Olieslagers another bad named test case has sneeked passed this PR

def test_fail_dump_tosa_ops(capsys, test_data: input_t1):
   ...
    pipeline = EthosU55PipelineINT[input_t1](...

I do not know why the test-arm-ootb-linux tests fails :(

[Michiel-Olieslagers]

I believe with our current test names we will encounter a lot of errors within the tosa & no_target jobs. I am currently working on a patch to implement a stricter naming convention to resolve this issue in the future. Regarding the ootb tests, I will need to investigate this a little bit more as this isn't linked to this issue.