Write Kuiper Image with configuration and no BOOT.BIN or *dtb files of selected configuration copied in /BOOT

[AAndrisa]

Environment:
OS: Windows
SW Version: Version: v1.0.0-rc3

Writing and configure a Kuiper Image in the same step, won’t copy BOOT.BIN and system.dtb in /BOOT after the writing process is completed

Steps to reproduce:

1. Click on "Image Source (Unconfigured)."
2. Select "ADI Kuiper Linux" from the list. Select image released on 2021-07-28.
3. On "Target (Unconfigured)," select "xilinx" >> "zynq" >> "zc706" >> "fmcomms2"
4. Click "Write."

Expected behavior:
After Kuiper image is written on SD card, it should be also configured

[jpineda3]

Same behavior on Ubuntu when configuring together after write option. The SD card is still properly written and can be configured at another process.

[tagoylo]

The same behavior is observed on macOs. The question here is, should this feature be enabled when writing Kuiper Image?

[ssmith73]

Same issue on Windows, configuring ZedBoard - no selected configuration files are written to /boot