al.compilationOptions.outFolder does not work as expected for apps without previous version

[RadoArvay]

1. Describe the bug

There is still kind of issue with al.compilationOptions.outFolder setup when building/publishing apps if previous version (for cop checks) does not exist yet. It is not possible to publish the app in that sitaution.
But there is also a strange behaviour when building/publishing apps if al.compilationOptions.outFolder is not setup at all.

It might relate to #7662 (about recommendations in the discussion) - maybe I missed some setting or it is a behaviour by design...I do not know.
But for #7536, it works.

2. To Reproduce
There is the setup in a workspace configuration:

"al.packageCachePath": "../.alpackages"
"al.compilationOptions": { "outFolder": "../.albuilds" }

AppSource Cop is active.
There is also the setup in AppSourceCop.json:

"baselinePackageCachePath": "../.appsourcepackages"

WITHOUT (!!!) version property because it is the first version of the app.
(I also tried to remove baselinePackageCachePath, but the result was the same.)

The app has few dependencies defined in app.json.

3. Expected behavior

To publish the app.

4. Actual behavior

When I try to build or publish, .app and .dep.app files are created in .albuilds folder, BUT also zero-sized .app file is created in .alpackages folder. And in a publish mode, launch-configurations-selector is not shown and therefore the app cannot be published (probably because of that zero-sized file).
When I run Publish full dependency tree... command, then it works and all apps are published.

NOTE: Even without al.compilationOptions.outFolder setup, .app file is created (but the correct one) to .alpackages folder - ONLY for the apps without previous version defined in AppSourceCop.json. So there is always a issue for "the first-time-runner".

5. Versions:

• AL Language: 14.2.1249978 or 15.0.1252955

I do not want to remove al.compilationOptions.outFolder so I am going to try and set up version property in AppSourceCop.json and build an empty "previous" app with a fake (0.0.0.0 or like that) version.

[RadoArvay]

I did a few other tests releated to the last paragraph and I found out strange behaviour:
If the version of the app is 1.0.0.0, it DOES NOT work. If it is any other version (0.0.0.0, 0.0.0.1, 1.0.0.1, 2.0.0.0), it WORKS. Why??