[Glimmer2] Add more curly component tests

[chadhietala]

This adds more tests around custom ids and bindings. These cases seem to be
only tested by the {{#view}} helper and that is going away. To ensure
we are at least tracking this functionality I added some tests to the
curly-component integration tests.

[chadhietala]

Related to #13235. Part of #13127.

[rwjblue]

In {{foo-bar id=blah}}, we evaluate the value of blah and "freeze" it as elementId in the component instance.

elementId can't be changed, if it did change then any actions/events would stop working. The view registry is keyed on the elementId, and is used to look up action/event targets. So it is definitely possible to make changing the id/elementId work, but it would be a new feature.

---

As a complete separate aside, we should ensure that a test also exists in this file for:

let fooBarInstance;
this.registerComponent('foo-bar', {
  ComponentClass: Component.extend({
    elementId: 'blahzorz',
    init() {
      this._super(...arguments);
      fooBarInstance = this;
    }
  }),

  template: `{{elementId}}`
});

this.render('{{foo-bar}}');

this.assertComponentElement(this.firstChild, { tagName: 'div', attrs: { id: 'blahzorz' }, content: 'blahzorz'});

this.runtask(() => {
  expectAssertion(() => {
    fooBarInstance.set('elementId', 'herpyderpy');
  }, /can not change elementId/);
});

this.assertComponentElement(this.firstChild, { tagName: 'div', attrs: { id: 'blahzorz' }, content: 'blahzorz'});

[chadhietala]

Makes sense. Added this test. The only thing is that an EmberError gets thrown so expectAssertion is not the correct assertion as it won't be stripped in prod builds.

[rwjblue]

Ahh, gotcha. I wasn't sure if it was an assertion or an error.

[rwjblue]

This looks good, thanks for moving these tests. I left a comment explaining the behavior of id=foo, and suggested adding another test for changing elementId after render.

[chadhietala]

@rwjblue I think CI just needs to be kicked on this one. I had to do some interesting stuff to get the prod tests to pass. https://github.com/emberjs/ember.js/pull/13236/files#diff-c47395a5aaf92aa0a7edbfa812d4e0afR61

[rwjblue]

If only https://github.com/emberjs/ember.js/blob/master/packages/ember-views/lib/views/states/in_dom.js#L24 used assert this wouldn't be needed (you could use expectAssertion which does these checks internally).

This is good though, I'm just grumbling 😈

[rwjblue]

Kicked sauce labs job...