feat: Warn when the registry server starts with authentication disabled by AgentGymLeader · Pull Request #6512 · feast-dev/feast

The registry server accepts control-plane writes such as applying feature
views, which materialize user-provided transformation code on the registry
host. When authentication is disabled (auth type no_auth) it accepts those
requests unauthenticated, so it is only safe to run inside a trusted network
boundary. Nothing in the startup path signals this today.

Add a startup warning emitted when the auth manager type is NONE, plus a
unit test covering that the warning fires for NONE and stays silent for an
authenticated type. Behavior is otherwise unchanged.

Signed-off-by: FugoP <264910004+AgentGymLeader@users.noreply.github.com>