build(deps): bump the materialize group in /console with 2 updates

[dependabot]

Bumps the materialize group in /console with 2 updates: @materializeinc/sql-lexer and @materializeinc/sql-pretty.

Updates @materializeinc/sql-lexer from 26.8.0 to 26.11.0

Commits

• 861418c release: bump to version v26.11.0
• bcc66cb release: bump to version v26.11.0-rc.3
• 664cdf5 Revert [persist] Try and issue just one CaS for a shard at a time#34875 (#34937)
• 0997c4d release: bump to version v26.11.0-rc.2
• c954738 storage: close iceberg table-ready on inactive workers (#34917)
• d2d6214 release: bump to version v26.11.0-rc.1
• 2e943eb Explain for subscribes (#34912)
• 3c01fa7 LICENSE: update change date
• 4be2516 Merge pull request #34915 from teskje/index-mz_hydration_statuses
• 0814623 catalog: indexes to speed up dbt-adapter queries
• Additional commits viewable in compare view

Updates @materializeinc/sql-pretty from 26.8.0 to 26.11.0

Commits

• 861418c release: bump to version v26.11.0
• bcc66cb release: bump to version v26.11.0-rc.3
• 664cdf5 Revert [persist] Try and issue just one CaS for a shard at a time#34875 (#34937)
• 0997c4d release: bump to version v26.11.0-rc.2
• c954738 storage: close iceberg table-ready on inactive workers (#34917)
• d2d6214 release: bump to version v26.11.0-rc.1
• 2e943eb Explain for subscribes (#34912)
• 3c01fa7 LICENSE: update change date
• 4be2516 Merge pull request #34915 from teskje/index-mz_hydration_statuses
• 0814623 catalog: indexes to speed up dbt-adapter queries
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).