[NO GBP] Renames mob/camera to mob/eye and makes everything follow suit (#87684)

## Why It's Good For The Game

Clarity and consistency regarding DM's systems. 
Internally, `eye` is used for anything that controls the client's view.

![image](https://github.com/user-attachments/assets/7d1291e1-7a6a-4736-a14b-97834e89846f)
How `eye` is used in DM is consistent with how we use the term, so I
figured this would add clarity.

Being named mob/camera also makes it unclear exactly what it's doing.
The name implies that it would function similar to how mob/camera/ai_eye
does, but most of the time it's only used as... an eye.

My ulterior reason for this PR is that I want to clean up
mob/camera/ai_eye and it's subtypes after this.
## Changelog

🆑
server: mob/camera has been renamed to mob/eye, which may break
downstreams
/🆑

---------

Co-authored-by: Ghom <42542238+Ghommie@users.noreply.github.com>

code/game/objects/items/devices/multitool.dm

@@ -204,7 +204,7 @@
 	var/turf/our_turf = get_turf(src)
 	detect_state = PROXIMITY_NONE
 
-	for(var/mob/camera/ai_eye/AI_eye as anything in GLOB.aiEyes)
+	for(var/mob/eye/ai_eye/AI_eye as anything in GLOB.aiEyes)
 		if(!AI_eye.ai_detector_visible)
 			continue
 
@@ -253,7 +253,7 @@
 // copied from camera chunks but we are doing a really big edge case here though
 /obj/item/multitool/ai_detect/proc/surrounding_chunks(turf/epicenter)
 	. = list()
-	var/static_range = /mob/camera/ai_eye::static_visibility_range
+	var/static_range = /mob/eye/ai_eye::static_visibility_range
 	var/x1 = max(1, epicenter.x - static_range)
 	var/y1 = max(1, epicenter.y - static_range)
 	var/x2 = min(world.maxx, epicenter.x + static_range)