[Bug]: issue creating Arrays using TypeKit

[p-bakker]

Describe the bug

See this discussion: https://discord.com/channels/1247582902930116749/1375144881739272272

According to the discussion:

• array.create(type) === array.create(type); ought to yield true, but always yields false
• creating arrays using ${context.program}.array.create(type); yields an array instance without NameSpace and using these as type on ModelProperties will result in errors when emitting OAS or JSONSchema, due to duplicate names (likely icw @visibility options?)

Reproduction

See https://discord.com/channels/1247582902930116749/1375144881739272272

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[timotheeguerin]

Note on this

• should also apply to Record
• might be good to have $.type.instantiate(decl, args) that can be a generic template instantitation kit that array.create and record.create reuse
• Need to see the consequence of realm. e.g. a mutator would mutate the array into a new realm, should that still dedup

[witemple-msft]

See also: #7895