fix(jetson): log confirmation after applying br_netfilter on R39 (#2418)

The R39 apply path currently prints a single "loading br_netfilter"
line before running modprobe/sysctl/tee, all of which are silent
(their stdout is redirected to /dev/null). On success the script
exits quietly, leaving the operator without a confirmation that the
apply actually completed, which two sysctls were flipped, or where
the drop-ins were persisted. On failure, only the raw error from
whichever step tripped `set -e` is visible.

Add one structured info line at the end of the apply branch
summarising what was done and where state now lives. Keeps the
skip branch unchanged and does not affect R36/R38 logging (which
already gets output from update-alternatives / systemctl restart).

Useful for:
- confirming the script actually ran the expected code path (in
  particular, that it's the v4+v6 version, not an older v4-only
  build) when triaging future reports.
- documenting the on-host footprint for later cleanup / debugging.

Author: yanyunl1991

scripts/setup-jetson.sh

@@ -79,6 +79,7 @@ get_jetpack_version() {
           || error "Sudo is required to load br_netfilter and write /etc/modules-load.d and /etc/sysctl.d drop-ins."
       fi
       apply_br_netfilter_setup
+      info "br_netfilter applied: bridge-nf-call-{iptables,ip6tables}=1; persisted to /etc/sysctl.d/99-nemoclaw.conf + /etc/modules-load.d/nemoclaw.conf" >&2
     fi
     return 0
   fi