chore(deps): update dependency @blueprintjs/select to v6.0.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@blueprintjs/select (source)	6.0.6 -> 6.0.8

---

Release Notes

palantir/blueprint (@​blueprintjs/select)

v6.0.8

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coveralls]

Pull Request Test Coverage Report for Build 19381645024

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 39.81%

---

Totals
Change from base Build 19381621943:	0.0%
Covered Lines:	4845
Relevant Lines:	11257

---

💛 - Coveralls

[sentry]

Bug: Multiple versions of @blueprintjs/core and @blueprintjs/icons are installed, causing potential runtime conflicts.
_{Severity: HIGH | Confidence: 0.95}

🔍 Detailed Analysis

The dependency update introduces multiple versions of @blueprintjs/core (6.3.2 and 6.3.4) and @blueprintjs/icons (6.2.0 and 6.3.1) into the dependency tree. This occurs because @blueprintjs/datetime@6.0.6 requires older versions (@blueprintjs/core@^6.3.2, @blueprintjs/icons@^6.2.0), while the updated @blueprintjs/select@6.0.8 requires newer versions (@blueprintjs/core@^6.3.4, @blueprintjs/icons@^6.3.1). This can lead to runtime conflicts where components receive an unexpected version, styling issues due to differing CSS, and general component incompatibilities.

💡 Suggested Fix

Update @blueprintjs/datetime to a version compatible with @blueprintjs/core@^6.3.4 and @blueprintjs/icons@^6.3.1 to ensure a single, consistent version of each dependency is resolved across the project.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: yarn.lock#L1520-L1552

Potential issue: The dependency update introduces multiple versions of
`@blueprintjs/core` (6.3.2 and 6.3.4) and `@blueprintjs/icons` (6.2.0 and 6.3.1) into
the dependency tree. This occurs because `@blueprintjs/datetime@6.0.6` requires older
versions (`@blueprintjs/core@^6.3.2`, `@blueprintjs/icons@^6.2.0`), while the updated
`@blueprintjs/select@6.0.8` requires newer versions (`@blueprintjs/core@^6.3.4`,
`@blueprintjs/icons@^6.3.1`). This can lead to runtime conflicts where components
receive an unexpected version, styling issues due to differing CSS, and general
component incompatibilities.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

_{Reference_id: 2627182}