Add describe-by selector for resources with ID and NAME columns

[clobrano]

Summary

When describing Kubernetes resources that have both ID and NAME columns, users are now prompted to choose which identifier to use for the describe operation. This provides flexibility for resources where both identifiers are available.

Key Changes

• Added currentTabHasIDAndName() method to detect when a resource table has both ID and NAME columns
• Added openDescribeBySelector() to display a dialog asking users to choose between "Name" or "ID" for describing resources
• Refactored getSelectedResourceInfo() into a more flexible getSelectedResourceInfoBy(idColumn) that accepts a column parameter, with the original method now delegating to it
• Updated describeResources() to accept an idColumn parameter specifying which column provides the resource identifier
• Added handling for the "describe-by" selector result in handleSelectorResult() to trigger the describe operation with the user's choice
• Added comprehensive test coverage in app_test.go for the new functionality, including edge cases like nil resources and case-insensitive column matching

Implementation Details

• The describe flow now checks if both ID and NAME columns exist before prompting; if only one exists, it proceeds directly with the describe operation as before
• The selector defaults to NAME column when the idColumn parameter is empty, maintaining backward compatibility
• Namespace detection continues to work correctly when present in the table

https://claude.ai/code/session_011DhepXnDKGecoNaYYnKgWQ