Incorporate heapster-saw into saw-script

[glguy]

No description provided.

[eddywestbrook]

I guess I don't have a strong opinion about how much history to capture, especially since most of the development is in the heapster-saw repo as @glguy suggested. There have certainly been breaking changes in the API of heapster-saw that have required matching changes in saw-script, but I don't think it is crucial to track all of that, especially as a lot of that had to do with matching changes to the Prelude in the saw-core repo, which no longer exists.

To sum up, any squashing on saw-script changes seems fine to me.

[lisanna-dettwyler]

Notes from this morning:

• Merge strategy will be squash & archive, so the history will be kept in the repository (perhaps renamed?) and mentioned in the merge request description and merge commit message, but not directly attached to master. I'll take care of the actual git merging for this.
• Thoughts on branch name, either for this or for things like this that we'd like to keep around? I'd suggest keeping it simple and calling it heapster.
• Actions integration is still a WIP and I'll spend some time working through it today.

[eddywestbrook]

Well, all the CI passes. Can we finally merge this sucker?

Can followup after

[lisanna-dettwyler]

Let's do this