fix(container-pull): drop the dead redirect pin from fetch_tags

fetch_tags lost -L, so --proto-redir has nothing to act on. Leaving it there
reads as though redirects were considered and handled on that call, which is
misleading in a change about redirects.

Measured with a pass-through curl wrapper over the real --list-tags path: the
registry token request and the tags list both answer 200 in a single hop, as do
the ccid and image-registry-credentials calls, so nothing on that path wants a
redirect. That was against registry.crowdstrike.com; the gov registries were not
reachable from the test environment.

The convention is now uniform across all four scripts: --proto-redir appears on
exactly the curl invocations that pass -L.

Author: carlosmmatos-cs

bash/containers/falcon-container-sensor-pull/falcon-container-sensor-pull.sh

@@ -298,8 +298,12 @@ curl_command() {
 }
 
 fetch_tags() {
+    # No -L, so no --proto-redir either: with nothing following a redirect, the
+    # redirect protocol pin is dead and only makes it look as though redirects
+    # were handled here. Measured on registry.crowdstrike.com: every call on this
+    # path answers 200 in one hop, so there is no redirect to follow.
     bearer_result=$(echo "-u $ART_USERNAME:$ART_PASSWORD" |
-        curl -s --proto '=https' --proto-redir '=https' \
+        curl -s --proto '=https' \
             "https://$cs_registry/v2/token?account=$ART_USERNAME&scope=repository:$registry_opts/$repository_name:pull&service=$cs_registry" -K-)
     handle_curl_error $?
     registry_bearer=$(echo "$bearer_result" | json_value "token" | sed 's/ *$//g' | sed 's/^ *//g')