Upgrade tracked-maps-and-sets to 3.0.2

[balinterdi]

This is to eliminate accessing Ember on the global context which throwsan error in Ember 4.

[balinterdi]

@achambers It seems as there is no automated test run to set up. How do you usually decide if a PR is safe enough to be merged? Thank you.

[balinterdi]

This is more complicated than I'd originally thought:

1. tracked-maps-and-sets drops support for ember-source < 3.23 and node v10 (see here and here), so if this PR gets merged, it should only be released in a major update of this add-on.
2. I ran the ember-try tests locally and the ones that exercise Ember >= 4 fail because they seem to need ember-auto-import v2. Upgrading to that should probably be done in a separate PR, prior to merging this one. (Though this has nothing to do with this PR)

[achambers]

@balinterdi Sounds like we should have a Quest issue for making this addon support Ember 4. Also embroider I guess.

As for the tests, they used to be run. I wonder if it's to do with them previously running on Travis. Need to move over to GH Actions or something.

[balinterdi]

Sounds like we should have a Quest issue for making this addon support Ember 4. Also embroider I guess.

I don't think you need to do anything special with regards to supporting Embroider other than adding the embroider-safe and embroider-optimized scenarios to the ember-try configuration.

As for the tests, they used to be run. I wonder if it's to do with them previously running on Travis. Need to move over to GH Actions or something.

Makes sense, yes, that's what most add-ons do, as far as I can tell.

[herzzanu]

Closing in favour of #341