feat(api): add displayName and keywords to perpAnnotation

[damjankuznar]

Updates setPerpAnnotation based on the HL API changes as posted in https://t.me/hyperliquid_api/302:

For HIP-3 deployers: setPerpAnnotation now allows specifying displayName and keywords. Display name allows deployers to indicate a different name for frontends to use, and is not permanent. The L1 name is immutable and can never be changed. All API endpoints still use the L1 name, but interfaces may substitute the display name. hl.xyz will respect the display name if it reasonably represents the tracked asset (as determined by the L1 name), only includes visible ASCII characters, does not contain colons, and starts with an alphanumeric character. The key motivation is that the L1 name and display name should be consistent enough so as to not be misleading for users. Other interfaces may apply different rules. Keywords can be used as hints to match against searches. hl.xyz will respect keywords that reasonably represent the asset being tracked.

Note for deployers: setPerpAnnotation must set all fields on each edit. Previous settings are not persisted. Deployers should set displayName: null or keywords: [] to ignore the respective field. See https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/hip-3-deployer-actions for details.

Summary

• Add displayName (nullable string) and keywords (string array) to setPerpAnnotation action in perpDeploy exchange method
• Add optional displayName and keywords fields to PerpAnnotationResponse info type
• Update tests to cover the new fields

[nktkas]

LGTM