Process GameAssembly.dll and global.metadata.dll from runtime

[krulci]

Description

This is an enhancement on top of #611 as the previous pull request added submodules.

• Implemented Il2CppDumper version 6.7.40 as nuget.
  This was done locally using js6pak/dotnet-link
  Approval of this pull request will need to make krulci/Il2CppDumper@7e418fe as nuget
• Runtime module dump is implemented in Memory validation and runtime module dump Il2CppInterop#122
  This feature can be enabled in config with UseRuntimeAssemblies option
• Added ApplicationData as an option for IL2CPPInteropAssembliesPath option

Motivation and Context

• Il2CppInterop.Runtime+RuntimeModuleDump will retrieve GameAssembly.dll from current process handle after temporarily setting memory protection to execute_read_write. Memory protection will be restore to its original state after module memory is read.
• Il2CppInterop.Runtime+RuntimeModuleDump will fix all sections so it can be processed by Il2CppDumper.
• Il2CppInterop.Runtime+RuntimeModuleDump will also extract global-metadata.dat from current process handle.
  This feature is for games with global-metadata.dat embedded in GameAssembly.dll.
• Uses Il2CppDumper to process List<Mono.Cecil.AssemblyDefinition> since Cpp2IL is incompetent with memory dumped file.
• ApplicationData was added to reduce the need of initialization toolchain rerun for environment where BepInEx is removed upon exit.
• MetadataSignatureToScan and ObfuscatedMetadataHeaderOffset are a config entry that is supplied to Il2CppInterop.Runtime+RuntimeModuleDump for pattern matching. Default value is a relative consistent value starts from offset 252 of multiple global-metadata.dat investigated.
• MagicToFix is a config entry that is supplied to Il2CppInterop.Runtime+RuntimeModuleDump when the first 8 bytes of global-metadata.dat is obfuscated to determine global-metadata.dat's version.

How Has This Been Tested?

Tested with PrincessConnectReDive (JP)
Chainloader startup complete
Tested with Umamusume (JP)
Chainloader startup complete

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.