For what are likely safety reasons, the default action when calling or double-clicking a PS1 file is simply to open it for viewing, as distinct from older script formats like BAT and VBS files that actually execute in those situations. That change has likely saved quite a number of unintended executions from users who might have double-clicked on a PS1 file when they meant to single-click it or similar. In any case, since a PS1 file isn't an actual application and isn't executed as its default action, you need to call PowerShell itself as the external application, which means your $strRunAtEndApp line should look like this:
$strRunAtEndApp = 'C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe';
And then your $strRunAtEndArgs line should look like this:
$strRunAtEndArgs = '-executionpolicy bypass -noprofile -nologo -file "D:\Windows-PC.Data-Image Script.ps1"';
If you wanted to be able to do this from within the script generation wizard, you would have needed to specify C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe as the application file name and then this on the Parameters line:
-executionpolicy bypass -noprofile -nologo -file "D:\Windows-PC.Data-Image Script.ps1"