make builtins_module a regular function, not a query

crates/red_knot_module_resolver/src/db.rs

@@ -1,8 +1,8 @@
 use ruff_db::Upcast;
 
 use crate::resolver::{
-    builtins_module, editable_install_resolution_paths, file_to_module,
-    internal::ModuleNameIngredient, module_resolution_settings, resolve_module_query,
+    editable_install_resolution_paths, file_to_module, internal::ModuleNameIngredient,
+    module_resolution_settings, resolve_module_query,
 };
 use crate::typeshed::parse_typeshed_versions;
 
@@ -12,7 +12,6 @@ pub struct Jar(
     module_resolution_settings,
     editable_install_resolution_paths,
     resolve_module_query,
-    builtins_module,
     file_to_module,
     parse_typeshed_versions,
 );

crates/red_knot_module_resolver/src/resolver.rs

@@ -46,8 +46,6 @@ pub(crate) fn resolve_module_query<'db>(
 /// Salsa query to return the Module for builtins.
 ///
 /// Can return None if a custom typeshed is used that has no `builtins.pyi`.
-#[allow(unreachable_pub)]
-#[salsa::tracked]
 pub fn builtins_module(db: &dyn Db) -> Option<Module> {
     let _span = tracing::trace_span!("resolve_builtins").entered();