Add TypeAliasTopLevel support to read_storage

[cabreraam]

This PR addresses Issue #2522.

I use pre-existing fields of TypeAliasTopLevel to handle using read_storage on aliased ElementaryType instances, e.g.,

type MyUint64 is uint64;
contract C {
    struct S {
        MyUint64 y;
        MyUint64 z;
    }
    S s;
}

AFAICT, this doesn't cover user defined types, but it seems like the above reproducer can be addressed by attributes of the TypeAliasTopLevel class.

This is the output I observe when I run get_storage_layout():

INFO:Slither-read-storage:
Contract 'C'
C.s with type C.S is located at slot: 0

INFO:Slither-read-storage:
Name: s
Type: C.S
Slot: 0

INFO:Slither-read-storage:
Contract 'C'
C.s with type C.S is located at slot: 0

INFO:Slither-read-storage:
Struct Variable: y
Name: s.y
Type: MyUint64
Slot: 0

INFO:Slither-read-storage:
Contract 'C'
C.s with type C.S is located at slot: 0

INFO:Slither-read-storage:
Struct Variable: z
Name: s.z
Type: MyUint64
Slot: 0

I couldn't get the test I added to run on my local machine, so I'll wait for the CI to run/if anyone has suggestions for changing things.

[CLAassistant]

All committers have signed the CLA.

[disconnect3d]

Shouldn't this perform some assertion?

[qci-cabrera]

Yes, for sure. I think when I was looking into this, it was just a skill issue, and I just wanted the test to run as some initial signal that was the changes I made didn't immediately break something.

I'd need to re-look at this, but absolutely, there needs to be some kind of assert to truly be meaningful.