Fix sub-fields accessing of generated structs

[yuancu]

Description

This PR fixes a bug where nested fields of generated structs (like those created by the geoip() function) were not accessible, returning incorrect field names and null values.

Problem

When accessing nested fields from generated structs using dot notation, the system would:

1. Return incorrect field names
2. Return null values instead of the actual nested field data
3. Return incorrect types

Solution

The fix involves two main changes:

QualifiedNameResolver.java:

• Fixed the joinParts calculation logic when creating item access for nested fields
• Added proper aliasing to preserve the original qualified field name in query results

Testing

• Added integration tests in CalciteGeoIpFunctionsIT.java to verify the fix
• Added YAML test cases to validate both logical and physical query plans
• Tests confirm that accessing info.dummy_sub_field now returns the correct field name and value

Related Issues

Resolves #4682

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[LantaoJin]

Did your merge upstream action happen before #4716 being merged?

[opensearch-trigger-bot]

The backport to 2.19-dev failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19-dev 2.19-dev
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19-dev
# Create a new branch
git switch --create backport/backport-4683-to-2.19-dev
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3a42c511cd08b2639f3c95441a9b7cac2f8ddb2c
# Push it to GitHub
git push --set-upstream origin backport/backport-4683-to-2.19-dev
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19-dev

Then, create a pull request where the base branch is 2.19-dev and the compare/head branch is backport/backport-4683-to-2.19-dev.

[opensearch-trigger-bot]

The backport to 2.19-dev failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19-dev 2.19-dev
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19-dev
# Create a new branch
git switch --create backport/backport-4683-to-2.19-dev
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3a42c511cd08b2639f3c95441a9b7cac2f8ddb2c
# Push it to GitHub
git push --set-upstream origin backport/backport-4683-to-2.19-dev
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19-dev

Then, create a pull request where the base branch is 2.19-dev and the compare/head branch is backport/backport-4683-to-2.19-dev.