[CI] Don't run SYCL testing for changes that only affect UR

[RossBrunton]

A number of changes to UR won't have any observable effects on SYCL
builds, so no point in running a full SYCL build and e2e test for them.

[martygrant]

couple files in the root dir we wouldn't want to run CI for like the README.md etc, from the discussion in this issue last year oneapi-src/unified-runtime#1511 maybe do the opposite and only run CI jobs if the change touches source, include and scripts?

[kbenzie]

couple files in the root dir we wouldn't want to run CI for like the README.md etc, from the discussion in this issue last year oneapi-src/unified-runtime#1511 maybe do the opposite and only run CI jobs if the change touches source, include and scripts?

Only needs to be include and source. If scripts changes result in different the code those will already be captured.

[kbenzie]

I think this workflow is also relevant sycl-detect-changes.yml as its the one that runs before the other workflows and decides which actually run.

[RossBrunton]

couple files in the root dir we wouldn't want to run CI for like the README.md etc, from the discussion in this issue last year oneapi-src/unified-runtime#1511 maybe do the opposite and only run CI jobs if the change touches source, include and scripts?

@martygrant A quick skim of the docs suggests that it's non-trivial to add rules to both "allow" and "disallow" paths, and such a thing feels like it would be confusing to understand. Also, if some new directory gets added in the future without updating this, I think it's better to accidentality run more jobs than to skip jobs that could fail.

I think this workflow is also relevant sycl-detect-changes.yml as its the one that runs before the other workflows and decides which actually run.

@kbenzie I had a look into that, but to use it I think I would have to have the job have a long list of contains(inputs.changes, 'llvm') && contains(inputs.changes, 'sycl') && .... The upside to doing this like this is that we don't need to run the SYCL pre-commit job, which means one less node needing to be allocated.

[aelovikov-intel]

Title needs to be updated. It's not all UR changes that skip CI.