Import does not make plugin package types visible by short name

A project that uses a plugin package can write an Import statement for the package's namespace, and the compiler accepts it, but the import has no effect on plugin types. Every plugin type reference still needs its fully qualified name: after Import Einhugur.Word, Var doc As Document fails with Unknown type 'Document' and the shared call Document.Create(path) fails with Undefined identifier 'Document', while Einhugur.Word.Document works.

Expected behaviour, per the language specification (section 9.4, Importing Modules And Namespaces): an Import makes the imported namespace's types visible by short name in the current lexical scope. This works for engine-declared namespaces today; plugin package types should behave the same way.

User impact: plugin consumers must fully qualify every reference to every plugin type, and the accepted-but-inert Import makes it look like the import should work.