feat: SyncVar hooks can have 2, 1 or no params

[imerr]

The weaver does this by generating a shim method with 2 params that calls the actual hook method

Not 100% sure if we actually want this for an extra 200 lines of weaver code

Tested with both mono&il2cpp builds (not tested virtual/static hook calls yet, will do if we plan on merging this)

[MrGadget1024]

Syntax changes

[MrGadget1024]

Suggested change

	void OnValueChanged(int oldValue)
	{
	HookCalled.Invoke(oldValue);
	}
	void OnValueChanged(int oldValue) => HookCalled.Invoke(oldValue);

[MrGadget1024]

Suggested change

	void OnValueChanged()
	{
	HookCalled.Invoke();
	}
	void OnValueChanged() => HookCalled.Invoke();

[MrGadget1024]

Remove blank line

Suggested change

[MrGadget1024]

Suggested change

	void OnValueChanged(int oldValue)
	{
	HookCalled.Invoke(1);
	}
	void OnValueChanged(int oldValue) => HookCalled.Invoke(1);

[MrGadget1024]

Suggested change

	void OnValueChanged(int oldValue, int newValue)
	{
	HookCalled.Invoke(2);
	}
	void OnValueChanged(int oldValue, int newValue) => HookCalled.Invoke(2);

[MrGadget1024]

Suggested change

	void onChangeHealth()
	{
	}
	void onChangeHealth() { }

[MrGadget1024]

Suggested change

	void onChangeHealth(int oldValue)
	{
	}
	void onChangeHealth(int oldValue) { }

[MrGadget1024]

Suggested change

	void onChangeHealth(int oldValue, int newValue)
	{
	}
	void onChangeHealth(int oldValue, int newValue) { }

[MrGadget1024]

Suggested change

	void onChangeHealth(int someOtherValue, int moreValue, bool anotherValue)
	{
	}
	void onChangeHealth(int someOtherValue, int moreValue, bool anotherValue) { }

[MrGadget1024]

Suggested change

	void onChangeHealth(int someOtherValue, int moreValue, int anotherValue, int moreValues)
	{
	}
	void onChangeHealth(int someOtherValue, int moreValue, int anotherValue, int moreValues) { }

[MrGadget1024]

Not 100% sure if we actually want this for an extra 200 lines of weaver code

It's only ~100 new loc excluding tests (which are great), and if we can deprecate the 2-param signature that will eventually remove almost as much code. Most cases don't need oldValue and newValue is always available in the SyncVar field itself because we always set that before invoking the hook.

Ideally, we should warn for 2-param hooks to advise users to have one param or none, while still allowing two params to compile and work as they do today so there's a transition window for existing projects.