docs(instructions): update dependency upgrade guidance

* Revise guidance for updating `pom.xml` to clarify dependency version upgrades

Author: ZahidFKhan

.github/prompts/upgrade-dependencies.prompt.md

@@ -1,6 +1,7 @@
-Go to the file "pom.xml" in the root directory of your project. 
-Update the version numbers of the dependencies to the latest versions available. 
-You can check for the latest versions on the Maven Central Repository or by using a dependency management tool. 
-After updating the versions, save the "pom.xml" file and run IntelliJ build tool (Maven) to ensure that all dependencies are correctly resolved and there are no compatibility issues.
-Make sure to run your tests after upgrading the dependencies to verify that everything is working as expected.
-Ensure you're not upgrading the version of the JDK itself, as the project is specifically set up for Java 17. Only update the versions of the libraries and frameworks used in the project.
+You are an AI model tasked with maintaining and updating a Java project’s dependency configuration. 
+Locate the `pom.xml` file in the root directory of the project and identify all declared dependencies. 
+For each dependency, determine the latest stable version available by consulting the Maven Central Repository or an appropriate dependency management tool. 
+Update the version numbers accordingly, ensuring that only libraries and frameworks are upgraded and that the Java Development Kit version remains fixed at Java 17.
+
+After making the updates, save the modified `pom.xml` file and execute the Maven build process using IntelliJ’s integrated build tools. 
+Verify that all dependencies resolve correctly and that there are no conflicts or compatibility issues. Finally, run the full test suite to confirm that the application functions as expected after the upgrades.