[debug] Fix hook snapshot command for nested hook paths

[riptide-01]

Overview

This PR resolves an issue where the shell-operator hook snapshot command did not work correctly for hooks located in nested directory paths.

What this PR does / why we need it

Closes #727

Changes made:

• Fixed hook snapshot command to properly handle nested hook paths
• Fixed CI warnings related to deprecated Ubuntu 20.04 image
• Fixed a bug where the shell-operator server started automatically without /shell-operator start command due to unwrapped start.go start function body in return.

Output of

/shell-operator hook snapshot 100-test/test.sh -o yaml

Before:

404 page not found

After:

kubernetes:
  operations:
    sinceLastExecution:
      count: 0
      added: 0
      deleted: 6
      modified: 12
      cleaned: 0
    sinceStart:
      count: 4
...

Command /shell-operator/ hook list works as before

["nested_folder/nested_hook.sh","root_hook.sh"]

Special notes for your reviewer

• Changes were tested in the Kubernetes cluster manually.

[Copilot]

Pull Request Overview

This PR fixes the snapshot command for hooks in nested directories, updates the CI runner image, and corrects the startup command wrapping to prevent unintended server startup.

• Enable hook snapshot to handle nested paths via regex-based routing
• Update GitHub Actions runner to Ubuntu 24.04 and resolve deprecation warnings
• Wrap the start function body properly to defer server startup until the explicit command

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 3 comments.

File	Description
pkg/shell-operator/debug_server.go	Replace specific Chi route with regex-based handler for nested paths
pkg/debug/server.go	Enhance format extraction from URI, add NotFoundError handling
cmd/shell-operator/start.go	Wrap startup logic in returned function to control server launch
.github/workflows/docs.yaml	Bump GitHub Actions runner from ubuntu-20.04 to ubuntu-24.04

Comments suppressed due to low confidence (2)

pkg/debug/server.go:159

• [nitpick] Defaulting an empty format to text/plain changes the previous default behavior (which was JSON). Confirm this new default is intended for all existing endpoints without explicit format parameter.

	case "":

pkg/shell-operator/debug_server.go:61

• The catch-all route "/hook/*" may intercept other hook endpoints (e.g., /hook/list). Consider narrowing the pattern to only match snapshot paths (for example /hook/*/snapshots{format:(json|yaml|text)}) or ensure route ordering prevents conflicts.

	dbgSrv.RegisterHandler(http.MethodGet, "/hook/*", func(r *http.Request) (interface{}, error) {