Docs jwt release note example

[anvithagowda098]

Summary

This PR improves the upgrade guidance for the TrafficPolicy API in the v2.2 release notes by adding a clear migration example for renamed authentication fields.

The current release notes mention that:

• jwt → jwtAuth
• apiKeyAuthentication → apiKeyAuth

However, they do not include an actionable example showing how to update existing TrafficPolicy resources.

This PR addresses that gap by adding:

• A warning callout about potential unexpected behavior when old fields are used after upgrade
• Before/After YAML examples for both JWT and API key authentication fields

Motivation

Users upgrading from v2.1 → v2.2 may not realize they need to manually update existing TrafficPolicy resources. Without migration examples, the change is easy to miss and can lead to misconfigured authentication policies after upgrade.

Change Type

/ kind documentation

Changelog

docs: add migration example for TrafficPolicy jwt/apiKey rename

[kristin-kronstain-brown]

The callout makes sense and the jwt → jwtAuth and apiKeyAuthentication → apiKeyAuth are correct. But the YAML is not accurate.

• JWTAuth (the type of jwtAuth) has only two fields: extensionRef and disable. The providers (NamedJWTProvider array) field belongs to the JWT type, which appears in GatewayExtensionSpec, not in TrafficPolicy. So in v2.2 you wire JWT providers via jwtAuth.extensionRef → a GatewayExtension whose spec.jwt.providers holds the list. jwtAuth.providers is invalid.
• APIKeyAuth has no providers field at all — it uses keySources, secretRef/secretSelector, forwardCredential, clientIdHeader, disable. So apiKeyAuth.providers (and the "before" apiKeyAuthentication.providers) is not correct.

[kristin-kronstain-brown]

Callouts need a blank line before them.