fix: leverage jdtutils to get project correct

[wenytang-ms]

resolve such issue according to data

• NoDeps [projectInfo] - get project path failure - leverage JDTUtils lib, at list the java version, project name and so on
• NotFound [importInfo] - get Project Path failure - leverage JDTUtils lib
• JDTUtils can also have high perfomance

[Copilot]

Pull Request Overview

This PR refactors the codebase to consistently use JDTUtils for project and resource resolution, improving reliability and performance when obtaining project paths and compilation units. The changes address issues where project information and import data could not be retrieved properly.

• Replaced manual URI parsing and resource lookup with JDTUtils methods
• Unified cache key format to use URIs instead of file paths
• Removed custom findProjectByPath method in favor of JDTUtils.findResource

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
ProjectResolver.java	Replaced ResourceUtils with JDTUtils for project resolution; updated cache keys to use URIs instead of file paths; removed custom project lookup method
ContextResolver.java	Changed resource accessibility checks to use JDTUtils.toUri; added support for getting URIs from class files (binary types)
ProjectCommand.java	Simplified compilation unit resolution by using JDTUtils.resolveCompilationUnit directly instead of manual file resource lookup

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.