Azure pipeline trigger: refactor paths logic

[lalver1]

The paths filter is used to select file paths to include or exclude from a pipeline trigger.

In the Infra pipeline, paths works as expected when branches only contains branches. However, it does not work as expected when branches includes tags since we have seen that the pipeline gets triggered when there have been no changes to the terraform infrastructure folder.

We need to move the logic from paths to another place, but how would we implement the file path filter? We would need to have a commit to use as a reference for diffing the terraform folder to see if there were any changes.

Acceptance criteria

• The Infra pipeline only runs when a tag has changes in the terraform folder