ci: Ignore Helm chart related files in images build pipelines

[ppawlowski]

Description

This pull request adds a configuration ti the container images build and deploy pipelines to ignore changes made in Helm chart-related files. As a result, images will not be built when changes to the Helm chart are the only ones introduced.

Related Issue(s)

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[github-actions]

node-red:3.1.x-main-linux-amd64 scan results

6 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
2 suites ±0   0 💤 ±0 
1 files   ±0   6 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

node-red:2.2.3-main-linux-amd64 scan results

26 tests  ±0    0 ✅ ±0   0s ⏱️ ±0s
 4 suites ±0    0 💤 ±0 
 1 files   ±0   26 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

node-red:3.0.2-main-linux-amd64 scan results

1 files  ±0  4 suites  ±0   0s ⏱️ ±0s
7 tests ±0  0 ✅ ±0  0 💤 ±0  7 ❌ ±0 
8 runs  ±0  0 ✅ ±0  0 💤 ±0  8 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

file-server:main-linux-amd64 scan results

1 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
4 suites ±0   0 💤 ±0 
1 files   ±0   1 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

node-red:3.0.2-main-linux-arm64 scan results

1 files  ±0  4 suites  ±0   0s ⏱️ ±0s
7 tests ±0  0 ✅ ±0  0 💤 ±0  7 ❌ ±0 
8 runs  ±0  0 ✅ ±0  0 💤 ±0  8 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

node-red:2.2.3-main-linux-arm64 scan results

26 tests  ±0    0 ✅ ±0   0s ⏱️ ±0s
 4 suites ±0    0 💤 ±0 
 1 files   ±0   26 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

node-red:3.1.x-main-linux-arm64 scan results

6 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
2 suites ±0   0 💤 ±0 
1 files   ±0   6 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

file-server:main-linux-arm64 scan results

1 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
4 suites ±0   0 💤 ±0 
1 files   ±0   1 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

forge-k8s:main-linux-amd64 scan results

1 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
4 suites ±0   0 💤 ±0 
1 files   ±0   1 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.

[github-actions]

forge-k8s:main-linux-arm64 scan results

1 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
4 suites ±0   0 💤 ±0 
1 files   ±0   1 ❌ ±0 

For more details on these failures, see this check.

Results for commit ef9b953. ± Comparison against base commit 4fedc21.