Fix missed gateway migration / add LocalAI env values / add test cert (#39)

[mattfsourcecode]

Migration from Ingress to Gateway API and TLS Configuration Updates

Overview

This PR finalizes the migration from Kubernetes Ingress to the Gateway API for the LocalAI deployment, a process originally intended to be completed in #2. It also introduces improvements to TLS testing capabilities and updates environment variables for the LocalAI depoyment.

Although concerns have previously been addressed in individual PRs, a DEVELOPMENT PAUSE has been declared in the README, with this PR focusing on resolving several outstanding issues that were in-progress when the pause went into effect. With this merge, #48 now blocks all future pull requests.

Key Changes

Completion of Gateway API Migration

• Removes legacy Ingress configuration from localai-values.yaml
• Implements Gateway API support in localai-values.yaml for enhanced traffic management
• Updates configuration to align with Gateway API best practices

LocalAI Environment Variables

• CONTEXT_SIZE=0: Disables token context limitations
• THREADS=4: Configures the number of CPU threads for model processing

TLS Configuration

• Adds test-certificate.yaml for TLS configuration testing

Testing

• Verified Gateway API functionality
• Tested TLS certificate generation
• Confirmed service connectivity
• Validated model persistence

---

Closes #39