[Bug]: testInteractive --scope triggers an assert on AtomicObjects

[jabraham17]

I am finding that running only the dyno scope resolver hits an assert on AtomicObjects.

> testInteractive modules/packages/AtomicObjects.chpl --scope
frontend/include/chpl/resolution/scope-types.h:289 in LookupResult] Assertion failed: !nonFunctions_ || found

I ran into this because both chplcheck and chpl-language-server crash when trying to scope resolve this file.

Its far easier to instrument chplcheck, so I added the following to UnusedFormals and found where the bug was being thrown

...
for use, _ in chapel.each_matching(root, Identifier):
            print(use.unique_id(), use.parent().unique_id())
            refersto = use.to_node()
            print(refersto)
...

The assert is being hit when scope resolving ABA. I then removed forwarding this.getObject()!;, which resolved this assert.

I then started getting asserts in AtomicObject.init. Removing all of those inits, I get asserts from AtomicObject.readABA. After this, I gave up looking for a "clean scope resolution"