Support FQDN in exists/changes

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Thisis a follow up issue from the discussion #346960 (comment 1194366601)

Problem

Copying the comment from the upstream issue, which is the way we evaluate rules with files (exists/changes)

1. We include the included files.
   • If an include statement has some rules, those rules are evaluated here.
   • This happens in the project context that has the include keyword.
2. We generate the final merged YAML.
3. Then we evaluate job rules just before creating the pipeline and decide if a job is included or not.
   • This happens in the main project context because the main project runs the final pipeline.

This is very confusing for the users since its very hard to tell what is the project context where rules are evaluated

Proposal

Use fully qualified domain name when using includes: and includes:rules so users could specify which file they would like to evaluate