Feature: App Launcher - service type detection needed in URL assembly logic

[chase-weiser88]

Current Behavior

When launching an application through the App Launcher with a NodePort service, the extension uses Rancher's proxy URL format:
/k8s/clusters/[cluster-id]/api/v1/namespaces/[namespace]/services/http:[service-name]:80/proxy/

This causes issues with applications that expect to be served from the root path (/).

Desired Behavior

App Launcher should detect the service type (NodePort, LoadBalancer, ClusterIP) and adjust the launch URL accordingly:

• For NodePort services: Use http://[node-ip]:[nodePort]
• For proxy URLs: Keep current behavior
• For Ingress: Keep current behavior

Using the Rancher demo application (monachus/rancher-demo):

• Direct NodePort access works: http://rancher-demo.cweiser.com:30021
• Current proxy URL fails: https://rancher.cweiser.com/k8s/clusters/c-m-xds5xzdt/api/v1/namespaces/cweiser/services/http:scale-np-service:80/proxy/

[krumware]

@chase-weiser88 @dcharles525 you might be able to collab on this alongside the minor release for the Rancher 2.10 updates

[dcharles525]

@krumware @chase-weiser88 yeah I can take a look at this for the minor release.