Improve inline constructor handling of 'if', 'try' and 'while' expressions.

[basro]

This PR adds special cases for if try and while expressions in the constructor inliner logic allowing for the body of those expressions to result in an inlined object with the condition that the expressions themselves are ignored (not assigned to a variable or passed as argument to some other function)

Example of code that used to cancel inlining but now works:

class ExternInlineClass {
	public var a = 1;
	public extern inline function new() {
	}
}

class Test {
	static var condition = false;
	static function main() {
		var a = new ExternInlineClass();

		if ( condition ) a; else a;

		while ( condition ) a;

		try { a; } catch(_) { a; };
		
		return a.a;
	}
}

A scenario where you'd encounter this problem is when you have a function that does some side effect and then returns an inline object. Even if the inline object was not used, just by being present at the end of an if or while block it would cause the inlining to cancel.

if (condition) doSomethingAndReturnInlinedObject();

This could be worked around by changing the body of the if to result in a noop:

if (condition) {doSomethingAndReturnInlinedObject(); null; }

With this PR that work around is no longer needed.

[Simn]

Please rebase to make the mac build failures go away!

[Simn]

@basro Please check if the linked commit makes sense to you! It seemed wrong to consider IEHIgnored as captured = true, so I flipped that. See the added test case for how it went wrong.

Edit: Looking at the example again, this might not be correct... My thinking was that this doesn't fail without the inline constructor algorithm, but that's only because the analyzer eliminates block-level array declarations and replaces them with their individual values. It could be argued that this should fail either way, so yeah, please take a look some time and feel free to revert my change!