Add Support for Group Name Selection in the MCP tools for Java Package

**Requirement:**
For Java v2 packages, we will use a new `groupId` while keeping existing package name (e.g. using com.azure.v2). User should be able to select the package name along with the group name while releasing a package.

**Task:**
As discussed with @praveenkuttappan, we've added a new field to the release dev-ops work items, i.e. `Custom.GroupId`. This task is to update the `azsdk-cli` tools to support the `Group` name match along with the `Package Name` while identifying the correct Java package.

Start in the azsdk-cli tools and trace how release DevOps work items identify the Java package from its Package Name. Check how the Custom.GroupId field is read, then verify that package selection matches both the package name and group name for Java v2 releases.

Written by the indexing model from the issue text.