build actions to use heaps 1.10.0 explicitly

[MondayHopscotch]

Using the git version of heaps exposes the build actions of this repo to potential instability as things change. This explicitly uses the 1.10.0 release to provide some stability in the deps required.

[MondayHopscotch]

This workflow isn't going to work, as there is a chicken-and-egg problem here. The workflow uses the master version of the composite file, but the updated composite file has to be merged into master before it can be used.

[AustinEast]

Hey! Very much appreciate the investigation/PR here. Been on a bit of an online sabbatical but happy to approve now :)

[MondayHopscotch]

Welcome back! I'm digging into the shape collision stuff that was reverted to see if I can figure out what's going on. However, setting things up locally, I'm seeing the same C:\HaxeToolkit\haxe\lib\heaps/2,0,0/h3d/impl/ShaderCache.hx:14: characters 33-34 : Unexpected ? build errors coming out of heaps 2.0.0 that was occurring with the master checkout of the heaps library. This PR originally went with 1.10.0 as that was a version that didn't appear to have that issue. Have you tested the build with 2.0.0 and seen it not have that build issue? Not sure if it's somehow related to other deps I have in my local environment, but for now I'm explicitly using 1.10.0 while working on this locally, but figured I'd ask since I saw a commit to use 2.0.0 for the build action.

[AustinEast]

That may be an issue from a local dependency 🤔 I did test with/without #41 on both 1.10.0 and 2.0.0, and the issue appeared on both versions of heaps for me!

[MondayHopscotch]

Strange, for me, if I have heaps 2.0.0, when I run haxe test.hxml, I throw that error. It's the same error I was seeing when I put the original PR when the github action would run.

[AustinEast]

Interesting! Which version of haxe are you on btw?

[MondayHopscotch]

I'm running 4.2.5 locally, and it looks like the build action for the repo was using 4.2.4 according to the logs here