fix: SQL name resolving

[aljazerzen]

A result of tedious pg_dump debugging.
Tests on Postgres 15 were failing becuase they are using pg_dump 15,
which was producing the following statements that were
not produced by pg_dump 14:

CREATE TYPE edgedb."__SchemaAccessPolicy" (
    INTERNALLENGTH = variable,
    INPUT = array_in,
    OUTPUT = array_out,
    RECEIVE = array_recv,
    SEND = array_send,
    ANALYZE = array_typanalyze,
    ELEMENT = edgedb."_SchemaAccessPolicy",
    CATEGORY = 'A',
    ALIGNMENT = double,
    STORAGE = extended
);

Applying these dumps failed because type
edgedb."_SchemaAccessPolicy" did not exist.

After digging in pg_dump source code a bunch, trying to figure out
why these statements were showing up, I found a query similar to this:

select
  typname,
  (
    SELECT typarray FROM pg_type te WHERE oid = pg_type.typelem
  ) = oid AS isarray
from pg_type;

After inspecting the results, I found that our resolver does not match
pg_type.typelem to the outer pg_type (as it should), but to the inner
pg_type, even though the inner pg_type has an alias which should make
the orignal name inaccessible.

So that's the bug. With an easy fix.
Turns out that when I implemented the resolver I did not know this detail,
becuase we even had a test for it.

[aljazerzen]

Ref #5697

[msullivan]

Nice detective work here