Merge default types into modules with the same name (query builder)

[CarsonF]

Given the schema

module default {
  type User {
    required status: User::Status;
  }
}
module User {
  type Status extending enum<Active, Disabled>;
}

In EdgeQL we can do

insert User {
  status := User::Status.Active
}

However, with the query builder the User type was not flattened because there's a module named User.
So we had to do

e.insert(e.default.User, {
  status: e.User.Status.Active,
});

With this PR we can do

e.insert(e.User, {
  status: e.User.Status.Active,
});

Which more closely matches EdgeQL

[scotttrinh]

Do you mind adding a quick test case to the LTS schema here? You can add a new dummy type and dummy module with a type and add a low-effort test to the select tests there to ensure all of the type inference works out? If not I can stick it in my todo list.

[CarsonF]

Absolutely, and thanks for the starting point. Wanted to get the concept in front of you before putting more work in.

[CarsonF]

Should this be frozen? Following suit of

edgedb-js/packages/generate/src/syntax/path.ts

Line 433 in d99c022

return Object.freeze(expr) as any;

[scotttrinh]

Oh, good question. I assume the expression at internalName is indeed a frozen object, so it would make sense to match there. Yeah, let's do that, the tests should catch any weird regressions there since we have that new User module from the test commit.