### Godot version

v4.0.alpha11.official [afdae67cc] (when the feature was added) and newer (still happens in RC6)

### System information

Windows 10

### Issue description

I'm unable to handle when the user sets an exported node property (this feature: https://github.com/godotengine/godot/pull/62185) from a setter in the editor (tool script).

I don't know if this is intentional or not, but for me it was unexpected. I had to revert back to `NodePath`s.

### Steps to reproduce

- Create a scene
- Attach a script to a node
- Add `@tool` at the top of the script
- Export a node property with a setter, preferably with an easy way to see if it executed:
	```
	@export var node:Node:
		set (mod_value):
			prints("node", mod_value)
			node = mod_value
	```
- Save, close and open again the scene to make sure the tool script is running in the editor
- Set the node property from the inspector
- Observe that the setter didn't run

The setter is not bypassed when running the game, it is only bypassed in the editor.

We can compare with a `NodePath` property, which setter is not bypassed regardless if it is in the editor or in game runtime.

### Minimal reproduction project

[nodepath.zip](https://github.com/godotengine/godot/files/10840411/nodepath.zip)

}
				}
				Variant v2 = d[k];
				if (v2.get_type() == Variant::ARRAY || v2.get_type() == Variant::DICTIONARY || v2.get_type() == Variant::OBJECT) {
					if (_find_recursive_resources(v2, resources_found)) {
						return true;
					}
				}
			}
		} break;
		case Variant::OBJECT: {
			Ref<Resource> r = v;
			if (r.is_null()) {
				return false;
			}
			if (resources_found.has(r.ptr())) {
				return true;
			}
			resources_found.insert(r.ptr());
			List<PropertyInfo> plist;
			r->get_property_list(&plist);
			for (const PropertyInfo &pinfo : plist) {
				if (!(pinfo.usage & PROPERTY_USAGE_STORAGE)) {
					continue;
				}
				if (pinfo.type != Variant::ARRAY && pinfo.type != Variant::DICTIONARY && pinfo.type != Variant::OBJECT) {
					continue;
				}
				if (_find_recursive_resources(r->get(pinfo.name), resources_found)) {
					return true;