Remove marshal method classification from outer build

Classification is now done entirely in the inner build's
RewriteMarshalMethods task. The outer build's FindJavaObjectsStep
no longer creates a MarshalMethodsClassifier, which was producing
spurious warnings when scanning already-rewritten assemblies
(byte/bool mismatch in _mm_wrapper methods, missing connectors).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

src/Xamarin.Android.Build.Tasks/Linker/MonoDroid.Tuner/FindJavaObjectsStep.cs

@@ -22,8 +22,6 @@ public class FindJavaObjectsStep : BaseStep, IAssemblyModifierPipelineStep
 
 	public bool ErrorOnCustomJavaObject { get; set; }
 
-	public bool UseMarshalMethods { get; set; }
-
 	public TaskLoggingHelper Log { get; set; }
 
 	public FindJavaObjectsStep (TaskLoggingHelper log) => Log = log;
@@ -114,11 +112,6 @@ List<CallableWrapperType> ConvertToCallableWrappers (List<TypeDefinition> types)
 			DefaultMonoRuntimeInitialization = "mono.MonoPackageManager.LoadApplication (context);",
 		};
 
-		if (UseMarshalMethods) {
-			var classifier = new MarshalMethodsClassifier (Context, Context.Resolver, Log);
-			reader_options.MethodClassifier = new MarshalMethodsCollection (classifier);
-		}
-
 		foreach (var type in types) {
 			var wrapper = CecilImporter.CreateType (type, Context, reader_options);
 			wrappers.Add (wrapper);

src/Xamarin.Android.Build.Tasks/Tasks/AssemblyModifierPipeline.cs

@@ -140,7 +140,6 @@ protected virtual void BuildPipeline (AssemblyPipeline pipeline, MSBuildLinkCont
 		var findJavaObjectsStep = new FindJavaObjectsStep (Log) {
 			ApplicationJavaClass = ApplicationJavaClass,
 			ErrorOnCustomJavaObject = ErrorOnCustomJavaObject,
-			UseMarshalMethods = EnableMarshalMethods,
 		};
 
 		findJavaObjectsStep.Initialize (context);