Fix branch elimination for macroDependencySatisfies

[mike-engel]

This is a follow up to #1468, and should fix ember-animation/ember-animated#647.

The problem is that #1468 only fixed branch elimination for non-runtime macros in JS/TS code via babel, but didn't fix it for templates via glimmer. This fixes macroDependencySatisfies by transforming it into a macroCondition in the first pass, which will eliminate the branch in the second pass when it's used as a sub-expression.

Writing code like macroCondition (macroDependencySatisfies 'qunit' '^2.8.0') will work, but is not ergonomic and is unfriendly.

I don't think this needs to be done for macroGetConfig or macroGetOwnConfig.

[NullVoxPopuli]

thanks for submitting this! looks like you have some test failures there!

[mike-engel]

Whoops, I thought they were all passing before I pushed.

@NullVoxPopuli I added an extra case to handle macro compositions, but it's starting to feel a little hacky. An alternative to this PR would be to expand the docs to call out explicitly that macroDependencySatisfies requires a parent macroCondition in templates to properly prune branches. That also feels a little hacky, but it's potentially less brittle.

[mansona]

Hey tests were failing on strange type problems so I rebased this 👍 I also re-targeted it to stable so we can get the bugfix out the door

[mansona]

Looks great 🎉

[mike-engel]

Wow, that was simple! Thanks @mansona