Feature Request: Add friendly_name display override for all Teleport resources

[salating]

Summary

Add a friendly_name field to all Teleport resource types that overrides the display name
shown in the UI without affecting the internal resource name, routing, or RBAC.

Problem

Teleport resource names have technical constraints (lowercase, unique identifiers,
auto-generated suffixes from LDAP discovery) that make them unsuitable as human-readable
display names. There is currently no way to show a friendly name in the UI without changing
the underlying resource name itself.

Proposed Solution

Add an optional friendly_name field across all resource types including but not limited to:

• windows_desktop_service hosts (auto-discovered and static)
• app_service applications
• node resources
• db_service databases
• kube_cluster resources

When set, friendly_name is displayed in the UI instead of name. The name field
continues to be used internally for all routing, RBAC, and addressing purposes.

Example

  - name: "resource-internal-name"
    friendly_name: "Human Readable Name"

Expected Behavior

• friendly_name displays in the Teleport UI wherever the resource name is shown
• friendly_name has no restrictions on character casing or formatting
• name continues to function as the internal identifier
• friendly_name is optional — existing behavior unchanged when not set