Automatically add debug builds as push, pull, and release event artifacts/assets

[pryrt]

Give plugin authors easy access to the "debug" builds of GUP.exe, so they can test their JSON edits to nppPluginList.json before submitting plugin to repo.

Automatically add debug builds to push and pull and release events:

• edit the existing CI_build to add debug artifacts to each push/pull(PR) build
• replicate to CD_release and store those debug zips as Assets on the Release

resolves #109

You can see an example of what it would look like in my fork: https://github.com/pryrt/wingup/releases/tag/vTry5
(And you would still be able to add your signed GUP.exe as Assets to the Release in the same way you always do.)

[pryrt]

Let me know if you want changes, like putting the "dbg" as a prefix rather than suffix on the zipfile name to make it more obvious that it's the debug build, or similar.

I included them on the CI_build for convenience; since push/pull actions will delete the artifacts per GitHub schedule, they wouldn't be there permanently, but might be useful to make sure that a not-yet-released GUP.exe doesn't break the process. But, if you'd prefer, I could revert that, and just have them in the new CD_release workflow, so that the debug Assets would only be on releases, not on other push/pull builds -- the Release Assets are a permanent storage, so they are the more necessary. But I thought that having it on the push/pull might be nice.

[donho]

@pryrt
Strangely they were queued (infinitly).
Whereas what I just approved to run #111 has done its checking.
Any idea for the block?

[pryrt]

@pryrt Strangely they were queued (infinitly)..... Any idea for the block?

It seems that one PR triggered 189 (which ran just fine) and 190 whch got stuck in the queued stage (and cannot be cancelled?).

I am hoping it was just a GitHub glitch that accidentally ran it twice. I will try creating a dummy PR from the same branch -- if it runs it (or queues it) twice again, then it's definitely something in my changes; if it only runs it once, then it was probably just a glitch on GH's end.

[pryrt]

#112 only ran it once (https://github.com/notepad-plus-plus/wingup/actions/runs/33888220052), even though it was the same exact code (I just duplicated the branch), so I am concluding it was just a GH glitch.

It's up to you whether you want to merge from #112, or from this one. Feel free to close whichever one you don't merge.

[donho]

It seems a glitch from Github - now All checks have passed.