sysbuild: packaging: Fix selection of application image path

[LuDuda]

Select the application image path based on encryption support, matching the behavior of zip packaging.

Tested using nRF54L15 and Matter OTA. This change only includes application image, as support for network core or mcuboot encryption is not present in the build system today. This addresses the customer needs.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 1

Inputs:

Sources:

sdk-nrf: PR head: fa2d7e6d187800603f987aac80750554a421aafd

more details

sdk-nrf:

PR head: fa2d7e6d187800603f987aac80750554a421aafd
merge base: bb876cddd6f5ff6b04e077c91c021144ab5e726e
target head (main): 2a3094035fa0c489daa852033cb2068c4e373ac6
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (1)

subsys
│  ├── bootloader
│  │  ├── cmake
│  │  │  │ packaging.cmake

Outputs:

Toolchain

Version: 53a57c4d75
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:53a57c4d75_bba2ea5f2e

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 559
• ✅ Integration tests
  • ✅ test-fw-nrfconnect-chip
  • ✅ test-fw-nrfconnect-tfm
  • ✅ test-sdk-find-my
  • ✅ test-sdk-mcuboot
  • ✅ test-sdk-dfu
  • ⚠️ test-fw-nrfconnect-nrf-iot_cloud

Disabled integration tests

• • test-fw-nrfconnect-nrf_lrcs_mosh
  • test-fw-nrfconnect-nrf_lrcs_positioning
  • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-proprietary_esb
  • test-fw-nrfconnect-ps-main
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-thread-main
  • test-low-level
  • test-sdk-audio
  • test-sdk-pmic-samples
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[NordicBuilder]

Memory footprint analysis revealed the following potential issues

sample.matter.template.debug[nrf5340dk/nrf5340/cpuapp]: ROM size increased by 2152[B] in comparison to the main[37cf8d1] branch. - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic)
sample.matter.template.debug[nrf52840dk/nrf52840]: ROM size increased by 2152[B] in comparison to the main[37cf8d1] branch. - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic)
sample.matter.template.release[nrf5340dk/nrf5340/cpuapp]: ROM size increased by 1596[B] in comparison to the main[37cf8d1] branch. - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic)
sample.matter.template.release[nrf52840dk/nrf52840]: ROM size increased by 1648[B] in comparison to the main[37cf8d1] branch. - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic)

Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-24225/1)