chore(deps): update dependency @blueprintjs/datetime to v6.0.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@blueprintjs/datetime (source)	6.0.8 -> 6.0.10

---

Release Notes

palantir/blueprint (@​blueprintjs/datetime)

v6.0.10

Compare Source

v6.0.9

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 20276129547

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.773%

---

Totals
Change from base Build 20276095058:	0.0%
Covered Lines:	4847
Relevant Lines:	11272

---

💛 - Coveralls

[sentry]

Bug: The handleParseDate function in GroundControlEditCell.tsx returns false on failure, but the @blueprintjs/datetime v6.0.10 parseDate prop expects null.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

In GroundControlEditCell.tsx, the handleParseDate function returns false when date parsing fails. However, the parseDate prop for the @blueprintjs/datetime v6.0.10 DateInput component expects a function with the signature (str: string) => Date | null. Returning false instead of the expected null violates the component's API contract. This mismatch can lead to incorrect error handling or other unexpected behavior within the DateInput component, as it may not correctly identify an invalid date parsing attempt.

💡 Suggested Fix

Modify the handleParseDate function in GroundControlEditCell.tsx to return null instead of false when the date string is invalid. Change return date.isValid() ? date.toDate() : false; to return date.isValid() ? date.toDate() : null;.

🤖 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#L1512-L1523

Potential issue: In `GroundControlEditCell.tsx`, the `handleParseDate` function returns
`false` when date parsing fails. However, the `parseDate` prop for the
`@blueprintjs/datetime` v6.0.10 `DateInput` component expects a function with the
signature `(str: string) => Date | null`. Returning `false` instead of the expected
`null` violates the component's API contract. This mismatch can lead to incorrect error
handling or other unexpected behavior within the `DateInput` component, as it may not
correctly identify an invalid date parsing attempt.

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