batches: implement pagination for batch_spec_workspace_steps.output_lines

[BolajiOlajide]

Reported here.
Closes #1800

A customer reported that steps in their spec output were truncated. Started debugging by trying this out with src-cli and inspecting the log output to confirm if the output was truncated from src-cli; it wasn't.
I then proceeded to debug via SSBC route and discovered we stored the complete output in batch_spec_workspace_execution_jobs.execution_logs and found out the resolver for BatchSpecWorkspace steps was paginated and this meant that when using the ${{ previous_step.stdout }} directive one wouldn't get the complete output from the previous steps and the output displayed was truncated.

The initial value for slicing the output lines was 500, I'm not 100% certain why that limit was placed but this PR removes the limit so we can get all lines in every step and also display the complete logs for users.

Test plan

Tested with a sample batch spec

name: brevity-2
description: Add Hello World to READMEs

# Find the first 100 search results for README files.
# This could yield less than 100 repos/workspaces if some repos contain multiple READMEs.
on:
  - repository: github.com/sourcegraph-testing/markdowns

# In each repository, run this command. Each repository's resulting diff is captured.
steps:
  - run: |
        for i in $(seq 1 1000); do
          echo "Hello world: $i"
        done
    container: alpine:3

  - run: |
      cat /tmp/stuff
    container: alpine:3
    files:
      /tmp/stuff: |
        ${{ previous_step.stdout }}

# Describe the changeset (e.g., GitHub pull request) you want for each repository.
changesetTemplate:
  title: Brevity test
  body: My first batch change!
  branch: brev
  commit:
    message: Testing Testing

Confirmed all output lines are displayed.

Loom

[sourcegraph-bot]

Codenotify: Notifying subscribers in CODENOTIFY files for diff b4a20e9...e854bf3.

Notify	File(s)
@courier-new	client/web/src/enterprise/batches/batch-spec/batch-spec.mock.ts client/web/src/enterprise/batches/batch-spec/execute/backend.ts client/web/src/enterprise/batches/batch-spec/execute/workspaces/WorkspaceDetails.module.scss client/web/src/enterprise/batches/batch-spec/execute/workspaces/WorkspaceDetails.story.tsx client/web/src/enterprise/batches/batch-spec/execute/workspaces/WorkspaceDetails.tsx cmd/frontend/graphqlbackend/batches.go
@eseliger	client/web/src/enterprise/batches/batch-spec/batch-spec.mock.ts client/web/src/enterprise/batches/batch-spec/execute/backend.ts client/web/src/enterprise/batches/batch-spec/execute/workspaces/WorkspaceDetails.module.scss client/web/src/enterprise/batches/batch-spec/execute/workspaces/WorkspaceDetails.story.tsx client/web/src/enterprise/batches/batch-spec/execute/workspaces/WorkspaceDetails.tsx cmd/frontend/graphqlbackend/batches.go

[github-actions]

❌ Problem: the label i-acknowledge-this-goes-into-the-release is absent.
👉 What to do: we're in the next Sourcegraph release code freeze period. If you are 100% sure your changes should get released or provide no risk to the release, add the label your PR with i-acknowledge-this-goes-into-the-release.

[sg-e2e-regression-test-bob]

Bundle size report 📦

Initial size	Total size	Async size	Modules
0.00% (0.00 kb)	0.01% (+2.05 kb)	0.02% (+2.05 kb)	0.00% (0)

Look at the Statoscope report for a full comparison between the commits e854bf3 and b4a20e9 or learn more.

Open explanation

• Initial size is the size of the initial bundle (the one that is loaded when you open the page)
• Total size is the size of the initial bundle + all the async loaded chunks
• Async size is the size of all the async loaded chunks
• Modules is the number of modules in the initial bundle

[github-actions]

❌ Problem: the label i-acknowledge-this-goes-into-the-release is absent.
👉 What to do: we're in the next Sourcegraph release code freeze period. If you are 100% sure your changes should get released or provide no risk to the release, add the label your PR with i-acknowledge-this-goes-into-the-release.

[github-actions]

❌ Problem: the label i-acknowledge-this-goes-into-the-release is absent.
👉 What to do: we're in the next Sourcegraph release code freeze period. If you are 100% sure your changes should get released or provide no risk to the release, add the label your PR with i-acknowledge-this-goes-into-the-release.

[courier-new]

That's cool, I've always wondered what a connection of scalar data would look like and how you'd query it. Turns out it's that simple! 😄

[eseliger]

looks good, I didn't try this out but trust you that you did :)

[courier-new]

Amazing, thank you so much for the refactor here!!