Patch method generation fail should not mark the patch as applied

[ghorsington]

This needs more testing but based on initial reports:

When patch method generation fails, it appears that the patch is still marked as applied. This is likely because patch info is saved into a global state before the patch method is updated:

HarmonyX/Harmony/Public/PatchProcessor.cs

Lines 159 to 169 in 66b8574

	var patchInfo = original.ToPatchInfo();
	patchInfo.AddPrefixes(instance.Id, prefix);
	patchInfo.AddPostfixes(instance.Id, postfix);
	patchInfo.AddTranspilers(instance.Id, transpiler);
	patchInfo.AddFinalizers(instance.Id, finalizer);
	patchInfo.AddILManipulators(instance.Id, ilmanipulator);
	var replacement = PatchFunctions.UpdateWrapper(original, patchInfo);
	PatchManager.AddReplacementOriginal(original, replacement);
	return replacement;

same for all other places where PatchFunctions.UpdateWrapper is called.

This causes more issues when trying to unpatch or add more patches in.

The logic should be refined as follows:

• Update the patch state
• Generate patch method and apply it
• If the patch method cannot be applied, revert the patch info to the previous state

A functionally more stable approach might be to back up the previous patch state so it can be quickly restored.