Fix fatal error when project reference objects have unexpected types for path and circular

[Copilot]

parseProjectReference used bare type assertions (v.(string), v.(bool)) that panic when tsconfig references entries contain non-string path or non-bool circular values:

{ "references": [{ "path": true }] }

Fix

Use comma-ok type assertions. When path is not a string, the reference gets an empty Path, which the existing caller logic already handles by emitting the "reference.path" requires type "string" diagnostic—matching TypeScript's behavior. Non-bool circular is silently ignored (defaults to false).

Copilot Checklist

I successfully ran these commands at the end of my session, and they completed without error:

• npx hereby build
• npx hereby test
• npx hereby lint
• npx hereby format