juliac: apply buildscript modifications after user code (#59297)

These modifications to the MethodTable should be performed at the
"link-stage", after all user top-level code has executed. This should be
closer to the upcoming 1.13 pipeline, which will move all top-level user
code to its standard package execution context.

This also makes any user-provided functionality for type printing
available to the `TrimVerifier`.

Resolves #59280.

Author: topolarity

contrib/juliac/juliac-buildscript.jl

@@ -2,10 +2,6 @@
 
 # Script to run in the process that generates juliac's object file output
 
-# Run the verifier in the current world (before modifications), so that error
-# messages and types print in their usual way.
-Core.Compiler._verify_trim_world_age[] = Base.get_world_counter()
-
 # Initialize some things not usually initialized when output is requested
 Sys.__init__()
 Base.init_depot_path()
@@ -23,10 +19,6 @@ if Base.get_bool_env("JULIA_USE_FLISP_PARSER", false) === false
     Base.JuliaSyntax.enable_in_core!()
 end
 
-if Base.JLOptions().trim != 0
-    include(joinpath(@__DIR__, "juliac-trim-base.jl"))
-end
-
 # Load user code
 
 import Base.Experimental.entrypoint
@@ -78,7 +70,12 @@ let mod = Base.include(Main, ARGS[1])
     end
 end
 
+# Run the verifier in the current world (before build-script modifications),
+# so that error messages and types print in their usual way.
+Core.Compiler._verify_trim_world_age[] = Base.get_world_counter()
+
 if Base.JLOptions().trim != 0
+    include(joinpath(@__DIR__, "juliac-trim-base.jl"))
     include(joinpath(@__DIR__, "juliac-trim-stdlib.jl"))
 end