refactor: upgrade aspect-gazelle, support incremental-build-protocol v3

[jbedard]

Changes are visible to end-users: no

Test plan

• Covered by existing test cases
• Manual testing; please provide instructions so we can reproduce:

[aspect-workflows]

Test

11 test targets passed

Targets

//integration_tests/aspect:configure_test [k8-fastbuild] 1m 55s
//integration_tests/aspect:flags_test [k8-fastbuild]     2m 7s
//integration_tests/aspect:help_test [k8-fastbuild]      1m 44s
//integration_tests/aspect:hints_test [k8-fastbuild]     1m 46s
//integration_tests/aspect:info_test [k8-fastbuild]      1m 24s
//integration_tests/aspect:init_test [k8-fastbuild]      214ms
//integration_tests/aspect:lint_test [k8-fastbuild]      1m 9s
//integration_tests/aspect:reenter_test [k8-fastbuild]   22s
//integration_tests/aspect:run_test [k8-fastbuild]       1m 20s
//integration_tests/aspect:telemetry_test [k8-fastbuild] 44s
//integration_tests/aspect:version_test [k8-fastbuild]   1m 31s

Total test execution time was 14m 6s. 80 tests (87.9%) were fully cached saving 9s.

---

Buildifier

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6648609116

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve fallback for pre-v2 watch clients

When the target connects with an older IBP client that negotiates v1 but watches sources, a watchman fresh-instance now sets cycleIsReset and reaches CycleReset; the upgraded server rejects that call for negotiated versions below v2 (CYCLE_RESET requires protocol >= v2), so the watch loop returns an error instead of notifying the target as it did before with a CYCLE/nil-sources message. This only shows up for source-watching targets built against the older protocol after a fresh-instance/recrawl, but it breaks backwards-compatible watch sessions.

Useful? React with 👍 / 👎.