Standardize plugins.TypedName field name from 'tn' to 'typedName'

[rohithnarasimha]

• Change LoraAffinityScorer to use typedName
• Change SLOAwareRouter to use typedName
• Update test mocks: mockAdmissionPlugin, testResponseReceived, testResponseStreaming, testResponseComplete, mockDataSource
• Improves consistency across all plugin implementations

Fixes #1910

What type of PR is this?
/kind cleanup

What this PR does / why we need it:

This PR standardizes the variable naming for plugins.TypedName fields across the codebase. Previously, both tn and typedName were used inconsistently. This change adopts typedName as the standard variable name for better code readability and consistency.

Changes include:

• Change LoraAffinityScorer to use typedName
• Change SLOAwareRouter to use typedName
• Update test mocks: mockAdmissionPlugin, testResponseReceived, testResponseStreaming, testResponseComplete, mockDataSource
• Improves consistency across all plugin implementations

Which issue(s) this PR fixes:
Fixes #1910

Does this PR introduce a user-facing change?:

NONE

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	1ab00e8
🔍 Latest deploy log	https://app.netlify.com/projects/gateway-api-inference-extension/deploys/693277a881b6d20008093cd4
😎 Deploy Preview	https://deploy-preview-1918--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: rohithnarasimha / name: rohith (1ab00e8)

[k8s-ci-robot]

Welcome @rohithnarasimha!

It looks like this is your first PR to kubernetes-sigs/gateway-api-inference-extension 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/gateway-api-inference-extension has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @rohithnarasimha. Thanks for your PR.

I'm waiting for a github.com 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.

[nirrozenbaum]

@rohithnarasimha thanks, looks good.
can you just sign your commits and fix the invalid commit message?

/ok-to-test
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nirrozenbaum, rohithnarasimha

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 [nirrozenbaum]

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

[k8s-ci-robot]

@rohithnarasimha: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

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.

[rohithnarasimha]

/retest-required

[rohithnarasimha]

@nirrozenbaum
I tried to remove cncf-cla = no but signing the document but still not updated
tried multiple times signing
can you please help on this

[elevran]

I tried to remove cncf-cla = no but signing the document but still not updated
tried multiple times signing
can you please help on this

There are separate issues:

1. missing CLA. Instructions in above comment. You need to sign (i.e., online acceptance) the CLA.
2. need signed commits. See instructions in the official GH docs.

[kfswain]

This looks great, TY!

[rohithnarasimha]

@nirrozenbaum The commit is now signed and verified, and CLA is complete. Could you please re-approve with /lgtm?

[nirrozenbaum]

/lgtm

Thanks! 🙏🏼