Bump to xamarin/Java.Interop/main@dd1ef455

Context: #6131 (review)
Context: fcb9ea3

Changes: http://github.com/xamarin/Java.Interop/compare/4fb7c147f8c6eb9bf94d9bfb8305c7d2a7a9fb33...dd1ef455ee4fbfa7e17f34c51cbe2ef24459e2e6

  * dotnet/java-interop@dd1ef455: Bump to mono/linker/main@b888d67 Mono.Cecil 0.11.4 (#861)

Commit fcb9ea3 didn't fix the build breakage.

Bump to xamarin/Java.Interop/main@dd1ef455 and set
`$(_XamarinAndroidCecilVersion)`, which will override the Mono.Cecil
NuGet package version within the Java.Interop build.

This will hopefully ensure/allow everything to now use Cecil 0.11.4.

TODO: This Quick-And-Dirty approach hardcodes
`$(_XamarinAndroidCecilVersion)`=0.11.4, meaning we now have two
different properties for the same thing:

	Directory.Build.props:    <MonoCecilVersion>0.11.4</MonoCecilVersion>
	build-tools/scripts/Configuration.Java.Interop.Override.props:    <_XamarinAndroidCecilVersion>0.11.4</_XamarinAndroidCecilVersion>

This is "undesirable".  Is there a way to update `xaprepare` so that
we can generate `external/Java.Interop/Configuration.Override.props`
so that `$(_XamarinAndroidCecilVersion)`=`$(MonoCecilVersion)`?

(Assuming that this approach even works…)

Author: jonpryor

build-tools/scripts/Configuration.Java.Interop.Override.props

@@ -1,6 +1,8 @@
 <?xml version="1.0" encoding="utf-8"?>
 <Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
   <PropertyGroup>
+    <!-- TODO: can we somehow grab the $(MonoCecilVersion) value in Directory.Build.props? -->
+    <_XamarinAndroidCecilVersion>0.11.4</_XamarinAndroidCecilVersion>
     <CecilSourceDirectory>$(MSBuildThisFileDirectory)..\..\external\mono\external\cecil</CecilSourceDirectory>
     <UtilityOutputFullPath>$(MSBuildThisFileDirectory)..\..\bin\$(Configuration)\lib\xamarin.android\xbuild\Xamarin\Android\</UtilityOutputFullPath>
     <UtilityOutputFullPathCoreApps>$(MSBuildThisFileDirectory)..\..\bin\$(Configuration)-net6.0\</UtilityOutputFullPathCoreApps>