Simplifying release packages

[ocornut]

Starting point:

dear_bindings_docking_clang_nogeneratedefaultargfunctions.zip
dear_bindings_docking_clang_withgeneratedefaultargfunctions.zip
dear_bindings_docking_gcc_nogeneratedefaultargfunctions.zip
dear_bindings_docking_gcc_withgeneratedefaultargfunctions.zip
dear_bindings_master_clang_nogeneratedefaultargfunctions.zip
dear_bindings_master_clang_withgeneratedefaultargfunctions.zip
dear_bindings_master_gcc_nogeneratedefaultargfunctions.zip
dear_bindings_master_gcc_withgeneratedefaultargfunctions.zip

(1) The Clang and GCC zip output are perfectly identical.
While it is sane that we keep test building with GCC on CI, it seems reasonable that we don't package both. It makes picking a package a little more daunting, and it suggest that the output is compiler dependent which seems confusing and misleading.

Will get us to:

dear_bindings_docking_nogeneratedefaultargfunctions.zip
dear_bindings_docking_withgeneratedefaultargfunctions.zip
dear_bindings_master_nogeneratedefaultargfunctions.zip
dear_bindings_master_withgeneratedefaultargfunctions.zip

(2) Do we have data on who is using what version?
Due to usage from C vs usage from other languages, I feel both should be kept. But perhaps while we apply (1) we could simplify the naming a little bit the appended string is a mouthful. I don't have a good suggestion for it yet, sorry!

(3) I have added backends to daily builds and releases, but this adds quite a few duplicate lines in the .yml file.
It would seem sane that we leverage and use the BuildAllBindings.sh script file from the CI actions, even if it might requires adding a few flags to it.

[ShironekoBen]

With regards to point 1, I wonder how relevant those artifacts are at all these days... if you drill down into Actions then you find them, but I would imagine most people will go for the Releases tab, which already has a relatively clean setup with one release for each ImGui branch (master/docking), and then the _nodefaultargsfunctions versions included as alternative files within those.

On 2... I'm afraid I certainly don't have any meaningful data there. I did ponder if nodefaultargsfunctions could be implemented as a #ifdef, but that would still leave the issue of ignoring them in the metadata as an exercise for the user.

And thanks for adding in the backends! It would be nice to use BuildAllBindings.sh, yeah - since there are now three places that all independently enumerate the list of bindings, combining them in some way would be nice. I'll have a poke and see if I can figure out a way to unify all that.