Type name resolution in the new metamodel support does not handle built-in types

[jeromesimeon]

Bug Report 🐛

Name resolution when importing a CTO file into its JSON syntax tree as instance of the Concerto metamodel does not handle built-in types (e.g., Concept, Participant etc).

Expected Behavior

Built in types should be resolved properly in the concerto namespace.

Current Behavior

Name resolution fails when importing a CTO model:

zsh-5.8$ ../concerto-cli/index.js import --input test/data/model/person.cto --resolve
10:06:47 AM - ERROR: Name Participant not found

Type name resolution fails on a declaration like this

namespace test

concept FOO {
  o Participant p
}