stop trying to resubscribe after max attempts

[craigmichaelmartin]

WHY are these changes introduced?

App log streaming sessions can become unstable due to network issues or authentication problems, causing repeated resubscribe failures that result in poor user experience with continuous retry attempts.

WHAT is this pull request doing?

Adds a maximum limit of 5 consecutive resubscribe failures before stopping app log polling and displaying a user-friendly message to restart the dev session. The implementation:

• Introduces MAX_CONSECUTIVE_RESUBSCRIBE_FAILURES constant set to 5
• Tracks consecutive resubscribe failures across polling cycles
• Resets the failure counter on successful operations
• Stops polling and shows "App log streaming session has expired. Please restart your dev session." when the limit is reached
• Applies this logic to both development polling and JSON log rendering modes

How to test your changes?

1. Start a dev session with app logs enabled
2. Simulate network connectivity issues or authentication failures that cause resubscribe failures
3. Verify that after 5 consecutive failures, polling stops and the appropriate message is displayed
4. Test that successful resubscribes reset the failure counter
5. Verify the behavior works in both UI and JSON output modes

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[craigmichaelmartin]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• stop trying to resubscribe after max attempts #7058 👈 (View in Graphite)
• Fix infinite 401 retry loop when app logs resubscribe fails #7055
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[craigmichaelmartin]

Decided to just fold this into #7055