Enhancements and fixes to the Java upgrade detection and notification in appmod plugin

[HaoZhang (haoozhang)]

What does this implement/fix? Explain your changes.

This pull request introduces several enhancements and fixes to the Java upgrade detection and notification features in the Azure Toolkit for IntelliJ plugin. The main improvements include better detection and reporting of Java version issues in Maven projects, improved notification logic, and new actions to streamline the upgrade process directly from the Problems View.

Java upgrade detection and notification improvements:

• Added a new JavaUpgradeProblemLocator utility to resolve and report Java version issues in Maven build files, including handling property references and nested property resolution.
• Updated the inspection logic in JavaUpgradeIssuesInspection.java to dynamically detect Java version problems in XML tags using Maven project properties, instead of relying solely on cached issues. [1] [2] [3]

Notification and quick fix enhancements:

• Improved the JavaUpgradeCheckStartupActivity to trigger upgrade checks after Maven project imports and to control when notifications are shown, preventing unnecessary alerts. [1] [2] [3] [4] [5]
• Enhanced the quick fix logic in JavaUpgradeQuickFix.java to select the appropriate Copilot agent and prompt format based on the specific upgrade reason (e.g., CVE vs. framework upgrade). [1] [2]

User interface and action improvements:

• Introduced a new UpgradeInProblemsViewAction that adds a context menu action in the Problems View, allowing users to trigger Copilot-powered upgrades for Java and frameworks directly from detected issues.

Dependency updates:

• Added mockito-core as a test dependency in the build configuration for improved unit testing capabilities.

Other fixes:

• Made JDK_LEARN_MORE_URL public for broader access.

Does this close any currently open issues?

https://devdiv.visualstudio.com/DevDiv/_workitems/edit/3054999/?view=edit

Any relevant logs, screenshots, error output, etc.?

Any other comments?

…

Has this been tested?

• Tested

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.