[GLIMMER2] Moves unbound tests

[chadhietala]

This moves the unbound tests to the new test infra and implements the unbound helper.

/cc #13127

[chadhietala]

Is it just me or is it weird that sexprs and syntax act differently when the parent re-renders?

[chadhietala]

Combination of

ember.js/packages/ember-htmlbars/tests/helpers/unbound_test.js

Lines 179 to 196 in bf067f7

	QUnit.test('it should render the current value of a property on the context', function() {
	equal(view.$().text(), 'BORK', 'should render the current value of a property');
	});
	QUnit.test('it should not re-render if the property changes', function() {
	run(function() {
	view.set('context.foo', 'oof');
	});
	equal(view.$().text(), 'BORK', 'should not re-render if the property changes');
	});
	QUnit.test('it should not re-render if the parent view rerenders', function() {
	run(function() {
	view.set('context.foo', 'oof');
	view.rerender();
	});
	equal(view.$().text(), 'BORK', 'should not re-render if the parent view rerenders');
	});

[chadhietala]

Opps will remove.

[chadhietala]

Combines https://github.com/emberjs/ember.js/blob/master/packages/ember-htmlbars/tests/helpers/unbound_test.js#L45-L54

[chadhietala]

Tests that were removed are:

Container lookup tests 1 2

Property With Attributes <--- Maybe bring this one back. This checks for property on an object where as another test just for property on the context.

[chadhietala]

@chancancode These are probably G2G given we are ok with the tests that were removed.

[chancancode]

✔️ it should not update the value if the parent view doesn't rerender

[chancancode]

✔️ should be able to render an bound helper invocation mixed with static values

[chancancode]

@chadhietala mostly looks good to me, left some feedback as line comments. I don't love the way the latter, more complicated tests are factored, the setup required are quite distracting and it took me a long time to understand what they do. It's not your fault though, and I think we don't have to worry about those now. Hopefully when everything settles someone will have the appetite to refactor these one day :P

[chancancode]

I'm a bit worried about the inconsistent semantics because our new implementation does not "naturally" have those problems, so I'll ask around in #core to figure out what we actually need to implement (w.r.t. rerender)

[chancancode]

(Oops)

[chadhietala]

I think CI just needs to be restarted. This fell victim to the left-pad debacle.

[homu]

☔ The latest upstream changes (presumably #13160) made this pull request unmergeable. Please resolve the merge conflicts.

[chancancode]

Can ✂️, I think?

[chancancode]

Looks great to me! There are a few minor things but they don't really need to block merging. However, I do want to hear from @rwjblue about the owner test before merging.