Remove geofence_enabled parameter from configuration files and update…

[jerinpeter]

This pull request updates how the geofence feature is enabled for the person follower module. Instead of configuring geofence enablement through YAML parameters, the setting is now controlled via the GEOFENCE_ENABLED environment variable. This change improves deployment flexibility by allowing geofence activation to be managed at runtime without editing configuration files.

Key changes:

Geofence enablement configuration:

• Removed the geofence_enabled parameter from all robot-specific YAML config files (go2_params.yaml, g1_params.yaml, tron_params.yaml). [1] [2] [3]
• Removed declaration of the geofence_enabled parameter in person_follow_greet.py.

Environment variable integration:

• Added GEOFENCE_ENABLED as an environment variable in the docker-compose.yml service definition, defaulting to false.
• Updated person_follow_greet.py to determine if geofencing is enabled by reading the GEOFENCE_ENABLED environment variable, rather than from parameters.