Import and export resolution improvements

[minestarks]

Fixes

• Fixed package exports - Export items weren't being generated in HIR for non-aliased exports, breaking libraries like FixedPoint
• Fixed relative namespace imports - import Bar from within namespace Foo now correctly resolves to Foo.Bar, matching the behavior of open Bar
• Fixed namespace reexports from dependency packages - Namespace aliases exported from a dependency's Main namespace (like export A as Alias) are now properly accessible to consuming packages
• Fixed declaration order dependencies - Import/export resolution now works regardless of the order namespaces are declared, using an iterative resolution approach

Breaking changes

• Primitive type exports (Unit, Qubit, Int) removed from legacy APIs - these never actually worked
• Parent namespace exports now explicitly banned (e.g. export Parent where Parent.Foo exists) - never properly worked
• Cross-namespace exports from external packages disallowed as they serve no purpose
• Duplicate imports/exports in namespace scope now consistently error - previously only some collisions would error
• Import name collisions with callable/UDT declarations now error

Library Cleanup

• Removed workaround aliases from FixedPoint and Rotations libraries that are no longer needed
• Cleaned up Microsoft.Quantum.Core legacy API exports

Implementation Notes

HIR:

• Removed redundant namespaces field from HIR - only resolver needs the namespace tree
• All import/export items now get item IDs; all exports are lowered while imports are not
• Export items now use Res type instead of ItemId to preserve even failed export items
• Simplified globals enumeration in global.rs

Parser & AST:

• Invalid patterns like import A.* as B, export C.*, and empty import; are now reported in the parser, reducing the validation that the resolver has to do
• Changed from "glob" to "wildcard" throughout codebase to match public documentation

Resolver:

• Iterative fixed-point algorithm resolves dependency chains between import/exports
• Simplified lowerer by moving more logic to resolver
• New public resolve() function encapsulates resolver API complexity

Language Service:

• Updated completion logic to work with new ImportKind structure, but no real fixes yet (next PR)

[github-actions]

Change in memory usage detected by benchmark.

Memory Report for 723f6a5

Test	This Branch	On Main	Difference
compile core + standard lib	24532482 bytes	25366182 bytes	-833700 bytes

[ScottCarda-MS]

I think I found a bug:

file A:

operation Original() : Unit {}

file B:

import A.Original as Other;

file C:

import B.Other;

File C will error saying it can't find B.Other. This is avoided if I put an export in file B: export Other as ExportedOther. Then file C can import B.ExportedOther;, but that seems like it shouldn't be necessary. My understanding was that exporting should really only be necessary to expose content across the package boundary.

[swernli]

Code overall looks good, signing off. Some feedback on from me (and Ian) that could address or discuss, but in general approach seems thorough and the new errors surfaced to the user are great.

[github-actions]

Change in memory usage detected by benchmark.

Memory Report for 5f1373f

Test	This Branch	On Main	Difference
compile core + standard lib	24532482 bytes	25366182 bytes	-833700 bytes

[orpuente-MS]

Approved with minor comment. Thanks!