Avoid unqualified-id "near" and "far" in Node3DEditor/Viewport

[TokageItLab]

Follow up #87164.

Current master build is failed by unqualified-id.

Previously this problem avoid by undef, but "near" and "far" are now reserved words generally, and that PR changed the reserved words in some files.

However other files also contained reserved words that needed to be changed.

(Although I feel Windows.h is too arrogant to use those common noun words as reserved words...🤔)

[fire]

This rename seems like it should have a small blast radius aside from git clutter.

[bruvzg]

There are a few more cases of "far"/"near" in the tests/scene/test_camera_3d.h:

godot/tests/scene/test_camera_3d.h

Lines 68 to 78 in 9050ee1

	constexpr float near = 0.2f;
	constexpr float far = 995.0f;
	constexpr float fov = 120.0f;
	constexpr float size = 7.0f;
	constexpr float h_offset = 1.1f;
	constexpr float v_offset = -1.6f;
	const Vector2 frustum_offset(5, 7);
	test_camera->set_near(near);
	CHECK(test_camera->get_near() == near);
	test_camera->set_far(far);
	CHECK(test_camera->get_far() == far);

[TokageItLab]

Now I believe all of them have been exterminated..

[akien-mga]

Some of those changes were likely not needed as there was:

core/math/aabb.cpp
121:#undef near
122:#undef far

servers/rendering/renderer_scene_render.cpp
51:#undef near
52:#undef far

scene/resources/camera_attributes.cpp
377:#undef near
378:#undef far

scene/debugger/scene_debugger.cpp
76:#undef near
77:#undef far

(added in fe4850c)

But I would then suggest to keep those changes and remove the #undefs which were added as hacky workaround.

[TokageItLab]

Alright, I removed #undef.

[akien-mga]

Looks great!

[akien-mga]

Thanks!