Move Control::accept_event to Node::accept_event

[L2750558108]

After #96867, the behavior of Control::accept_event and Viewport::set_input_as_handled will be the same. Control::accept_event could be a general way to handle input event, and replace get_viewport().set_input_as_handled() before in nodes except Control.

[AThousandShips]

You will need to add the following to the end of misc/extension_api_validation/4.3-stable.expected (with two empty lines after the last entry)

GH-96989
--------
Validate extension JSON: API was removed: classes/Control/methods/accept_event

Method moved to Node. Compatibility method registered.

[AThousandShips]

You need to pull your upstream changes and then apply your new changes, you just erased the previous changes you had made (remember to push with git push --force)

[Mickeon]

Assuming it still is accurate, the new description is a bit too vague... or wrong? I noticed it's identical to Viewport's, but... hm. For example, I remember that the actual order is dependent on the current input step, it's not always "down".

Suggested change

	Stops the input from propagating further down the [SceneTree].
	Stops the input event from propagating further in this node's viewport (see [method get_viewport]). This is equivalent to [method Viewport.set_input_as_handled] on this node's viewport.

[L2750558108]

Emm... I copy it from the Viewport::set_input_as_handled, since its behavior is the same as it. Is this means that the description in Viewport also need change?

[Mickeon]

Doesn't have to be done in this PR

[AThousandShips]

You used a merge commit to update your branch, please use rebase in the future instead, see here

[raulsntos]

Since the method moves from a derived type (Control) to a base type (Node), that doesn't break compat in C#.

I don't know if breaks compat for godot-cpp, but I feel like adding a compat method for a method that is removed doesn't really do anything because there's nowhere to add the compat hash in the extension_api.json.

So if the compat method is not needed for C++ I'd just remove it. If the compat method is needed, we'll likely need to figure out a way to add it to extension_api.json.

cc @dsnopek

[AThousandShips]

It is needed and it is the way things have been done before, but there was several ones moved to the hashes in #96586 so might be worth doing that here too

Edit: those were moved for different reasons though so unsure if it is valid here, and realized the cases I thought were moved were in fact changed differently, so don't know if we have any cases like this in the codebase at all

[Sauermann]

I remember a similar case in #68070, but it was merged for 4.0, so no compatibility functions were necessary.