feat: put the install dir on $GITHUB_PATH

Each `run:` step gets a fresh shell, and an Actions shell is neither a login
nor an interactive one, so nothing it starts reads the startup files the
installer edited. Appending the directory to the file $GITHUB_PATH points at is
the mechanism the runner does honour: it prepends those entries for every later
step. So `curl ... | sh` in one step and `flagsmith` in the next now works on
any runner, rather than only on images that already ship ~/.local/bin on PATH.

Taken from uv's Add-Ci-Path. The release smoke job drops its explicit sourcing
of the env script and relies on this instead.

beep boop

Author: khvn26

.github/workflows/release.yml

@@ -63,7 +63,4 @@ jobs:
         with:
           persist-credentials: false
       - run: sh install.sh --version "$GITHUB_REF_NAME" --bin-dir "$RUNNER_TEMP/bin"
-      - name: the env script puts it on PATH
-        run: |
-          . "$HOME/.local/share/flagsmith/env"
-          flagsmith --version
+      - run: flagsmith --version

install.sh

@@ -166,6 +166,14 @@ end
 EOF
 }
 
+# add_ci_path makes the CLI available to later steps of a GitHub Actions job.
+# GITHUB_PATH does not expand variables, so write the resolved directory.
+add_ci_path() {
+	[ -n "${GITHUB_PATH:-}" ] || return 0
+	printf '%s\n' "$INSTALL_DIR" >>"$GITHUB_PATH"
+	say "  added ${INSTALL_DIR} to \$GITHUB_PATH"
+}
+
 # add_source_line appends to a startup file, once.
 add_source_line() {
 	grep -qF "$2" "$1" && return 0
@@ -246,7 +254,10 @@ If ${VERSION} was released moments ago its archives may still be uploading — r
 		err "${INSTALL_DIR}/${BIN_NAME} was installed but will not run — wrong platform?"
 	say "installed ${installed} to ${INSTALL_DIR}/${BIN_NAME}"
 
-	[ "$NO_MODIFY_PATH" = 1 ] || modify_path
+	if [ "$NO_MODIFY_PATH" != 1 ]; then
+		modify_path
+		add_ci_path
+	fi
 
 	say ""
 	if [ "$PATH_MODIFIED" = 1 ]; then