feat: HTTP healthcheck on EKS GatewayServer

[fra98]

Description

• Remove the dedicated EKS gateway server template and unify into the single standard template. Instead of maintaining a separate Helm template for EKS, the EKS-specific NLB annotations (healthcheck config, load balancer type, scheme, etc.) are now injected via liqoctl install eks values.
• Add ServiceAnnotations and ServiceLabels fields to the GatewayServer CRD, allowing users to customize the gateway Service metadata directly from the CR spec without modifying the server template.
• Switch EKS healthcheck from TCP to HTTP (/healthz on port 8083), avoiding creating the extra dummy server (e.g., nginx) to pass the TCP health check
• Update docs to recommend the AWS Load Balancer Controller and document the legacy in-tree fallback annotations.

[adamjensenbot]

Hi @fra98. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• feat: 🚀 New Feature
• fix: 🐛 Bug Fix
• refactor: 🧹 Code Refactoring
• docs: 📝 Documentation
• style: 💄 Code Style
• perf: 🐎 Performance Improvement
• test: ✅ Tests
• chore: 🚚 Dependencies Management
• build: 📦 Builds Management
• ci: 👷 CI/CD
• revert: ⏪ Reverts Previous Changes

[fra98]

/rebase test=true

[fra98]

/rebase test=true

[fra98]

/test

[fra98]

/merge