feat: Update oke topology to match customer tenancy data, add example

[dkennetzoracle]

What type of PR is this?

/kind feature

What this PR does / why we need it:

1. OKE IMDS topology data - updated to match real customer topology information (HPC island, network block, local block, rack, GPU memory fabric) for topology aware scheduling.
2. Add H100 example

Which issue(s) this PR is related to:

#111 - doesn't close
#138 - adds a subset of this PR

Special notes for your reviewer:

This PR is split from #138 to remove ipv6 and focus on updating OKE to match real topology data. This was tested and validated on our BM.GPU.H100.8 shapes in a single-stack ipv4 RDMA cluster. A follow-up PR will be added to address ipv6 which is relevant for gb200+.

Does this PR introduce a user-facing change?

Update OKE to expose OCI RDMA topology attributes (HPC island, network block, local block, rack, GPU memory fabric) for topology-aware scheduling.

[k8s-ci-robot]

Hi @dkennetzoracle. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dkennetzoracle]

cc: @anson627 & @aojea - split the ipv6 PR and this one focuses on updated OKE RDMA topology attributes.

[aojea]

/ok-to-test
/lgtm
/approve

Thanks, ipv6 change has more architectural consequences and we strive for strong backwards compatibility, let's discuss separately

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, dkennetzoracle

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [aojea]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dkennetzoracle]

@aojea awesome, would you all prefer to discuss in slack or in the other PR? I haven't joined the slack but can do. I agree that will be a larger change.