Add type aliases for registries

Introduces `GlobalFunctionRegistry` and `GlobalAnalyzedRegistry` type
aliases to clarify the usage of `HashMap`s for storing global functions
and their analyzed versions. This change also refactors the
`LambdaCollector` and `Optimizer` to use these new aliases, improving
code readability and maintainability.

src/ast/compiler/optimizer/engine.rs

@@ -1,4 +1,6 @@
-use crate::ast::compiler::bound_nodes::{Address, AnalyzedNode, BoundKind, GlobalIdx, UpvalueIdx};
+use crate::ast::compiler::bound_nodes::{
+    Address, AnalyzedNode, BoundKind, GlobalAnalyzedRegistry, GlobalIdx, UpvalueIdx,
+};
 use crate::ast::nodes::Node;
 use crate::ast::types::{Purity, Value};
 use crate::ast::vm::Closure;
@@ -16,7 +18,7 @@ pub struct Optimizer {
     max_passes: usize,
     pub globals: Option<Rc<RefCell<Vec<Value>>>>,
     pub global_purity: Option<Rc<RefCell<HashMap<GlobalIdx, Purity>>>>,
-    pub lambda_registry: Option<Rc<RefCell<HashMap<GlobalIdx, AnalyzedNode>>>>,
+    pub lambda_registry: Option<Rc<RefCell<GlobalAnalyzedRegistry>>>,
 }
 
 impl Optimizer {
@@ -42,7 +44,7 @@ impl Optimizer {
 
     pub fn with_registry(
         mut self,
-        registry: Rc<RefCell<HashMap<GlobalIdx, AnalyzedNode>>>,
+        registry: Rc<RefCell<GlobalAnalyzedRegistry>>,
     ) -> Self {
         self.lambda_registry = Some(registry);
         self