docs: add balanced linter sections for all 5 linters

Replace verbose embedded-cluster section (148 lines) with comprehensive
"Linter-Specific Configuration" section covering all 5 linters (135 lines).

Each linter now has consistent documentation:
- Helm: Chart structure and template validation
- Support Bundle: Collector spec validation
- Embedded Cluster: EC config validation (trimmed from 148 to ~30 lines)
- KOTS: KOTS Config manifest validation (new, ~40 lines)

All sections include:
- What it validates
- Configuration example
- Auto-discovery behavior
- Key constraints (e.g., 1 config limit for EC and KOTS)

KOTS section highlights:
- GVK filtering distinguishes KOTS Config (kots.io) from EC Config
- Multiple config error message with actionable guidance
- Example KOTS Config manifest

Removed platform requirements for EC (Darwin support coming soon).

Author: Bishibop

docs/lint-format.md

@@ -298,151 +298,137 @@ spec:
 
 **Solution:** Either add the corresponding chart to your configuration or remove the unused HelmChart manifest. Warnings are informational and won't cause linting to fail.
 
-## Embedded Cluster Configuration
+## Linter-Specific Configuration
 
-The embedded-cluster linter validates Embedded Cluster configuration files. Embedded Cluster is Replicated's solution for packaging Kubernetes and your application together as a single appliance-style installer.
+### Helm Linter
 
-### What It Validates
+The Helm linter validates Helm chart structure, templates, and values files using the official `helm lint` command.
 
-The embedded-cluster linter validates:
-- Configuration schema correctness
-- Kubernetes version compatibility
-- Extension configurations
-- Network and storage settings
-- High availability settings
-- Custom branding configuration
+**What it validates:**
+- Chart.yaml metadata and format
+- Template syntax and rendering
+- Values file structure
+- Required files and directories
+- Kubernetes resource validity
 
-### Platform Requirements
+**Configuration:**
+```yaml
+repl-lint:
+  linters:
+    helm:
+      enabled: true
+      strict: false    # Set to true to treat warnings as errors
+  tools:
+    helm: "latest"     # Optional: pin to specific version (e.g., "3.14.4")
+```
 
-**Important:** The embedded-cluster linter binary is currently only available for **Linux AMD64**.
+**Auto-discovery:** Automatically finds charts by locating `Chart.yaml` files in your project.
 
-- ✅ **Linux (x86_64/amd64)**: Full support
-- ❌ **macOS**: Not currently available
-- ❌ **Windows**: Not currently available
-- ❌ **ARM64**: Not currently available
+---
 
-If you're on an unsupported platform:
-- The linter will fail gracefully with a clear error message
-- Other linters (helm, preflight, support-bundle) will continue running
-- Consider running in a Linux container or CI environment
+### Support Bundle Linter
 
-### Configuration
+The Support Bundle linter validates support bundle collector specs for Replicated's troubleshooting framework.
 
-Enable the embedded-cluster linter in your `.replicated` file:
+**What it validates:**
+- Collector spec syntax and structure
+- Analyzer definitions
+- Output redaction rules
+- Kubernetes resource collectors
 
+**Configuration:**
 ```yaml
 repl-lint:
-  version: 1
   linters:
-    embedded-cluster:
+    support-bundle:
       enabled: true
-      strict: false    # Set to true to treat warnings as errors
+      strict: false
   tools:
-    embedded-cluster: "latest"   # Optional: pin to specific version
+    support-bundle: "latest"   # Optional: pin to specific version
 ```
 
-### Auto-Discovery
+**Auto-discovery:** Finds support bundle specs by locating files with `kind: SupportBundle` or `kind: Collector`.
 
-When no `.replicated` config exists, the linter automatically discovers embedded-cluster configs by:
-- Finding files with `kind: Config` and `apiVersion: embeddedcluster.replicated.com/v1beta1`
-- Validating only 0 or 1 config exists (multiple configs are not supported)
+---
 
-### Multiple Config Validation
+### Embedded Cluster Linter
 
-**Only 0 or 1 embedded cluster config is allowed per project.**
+The Embedded Cluster linter validates Embedded Cluster configuration files for Replicated's embedded Kubernetes installer solution.
 
-If multiple configs are detected:
-- Each config will show as failed with a clear error message
-- Other linters (helm, preflight, support-bundle) continue running
-- The linting command returns a non-zero exit code
+**What it validates:**
+- Configuration schema correctness
+- Kubernetes version compatibility
+- Extension configurations
+- Network and storage settings
+- High availability settings
 
-### Example Configuration
+**Important constraint:** Only 0 or 1 embedded cluster config is allowed per project.
 
-**Minimal `.replicated` with embedded-cluster:**
+**Configuration:**
 ```yaml
-appId: ""
-appSlug: "my-app"
-manifests:
-  - "./embedded-cluster/*.yaml"
-
 repl-lint:
-  version: 1
   linters:
     embedded-cluster:
       enabled: true
-      strict: true
+      strict: false
   tools:
     embedded-cluster: "latest"
 ```
 
-**Example embedded-cluster config file (ec-config.yaml):**
-```yaml
-apiVersion: embeddedcluster.replicated.com/v1beta1
-kind: Config
-metadata:
-  name: my-app-config
-spec:
-  version: "1.33+k8s-1.33"
-  roles:
-    controller:
-      name: "Controller"
-      description: "Kubernetes controller node"
-
-  extensions:
-    helm:
-      repositories:
-        - name: my-repo
-          url: https://charts.example.com
-
-  network:
-    podCIDR: "10.244.0.0/16"
-    serviceCIDR: "10.96.0.0/12"
-
-  unsupportedOverrides:
-    k0s: |
-      apiVersion: k0s.k0sproject.io/v1beta1
-      kind: ClusterConfig
-      spec:
-        network:
-          provider: calico
-```
+**Auto-discovery:** Finds configs by locating files with:
+- `kind: Config`
+- `apiVersion: embeddedcluster.replicated.com/v1beta1`
 
-### Output Format
+**Multiple configs error:** If multiple configs are found, each will show as failed with a clear error message. Other linters continue running.
 
-The embedded-cluster linter returns JSON output with structured validation results:
+---
 
-```json
-{
-  "files": [
-    {
-      "path": "embedded-cluster/config.yaml",
-      "valid": true,
-      "errors": [],
-      "warnings": [],
-      "infos": []
-    }
-  ]
-}
-```
+### KOTS Linter
 
-**Validation Messages:**
-- **errors**: Schema violations, invalid values, unsupported configurations
-- **warnings**: Deprecated fields, potential issues, best practice violations
-- **infos**: Informational messages about configuration choices
+The KOTS linter validates KOTS Config manifests (custom resource for application configuration UI).
 
-### Troubleshooting
+**What it validates:**
+- Config schema correctness
+- Config group and item definitions
+- Field types and validation rules
+- Template syntax
+- Required vs optional fields
 
-**Problem:** "embedded-cluster binaries are only available for linux-amd64"
+**Important constraint:** Only 0 or 1 KOTS config is allowed per project.
 
-**Solution:**
-- Run linting in a Linux environment or Docker container
-- Use CI/CD on Linux runners
-- The error won't block other linters from running
+**Configuration:**
+```yaml
+repl-lint:
+  linters:
+    kots:
+      enabled: true
+      strict: false
+  tools:
+    kots: "latest"     # Optional: pin to specific version
+```
 
-**Problem:** "Multiple embedded cluster configs found"
+**Auto-discovery:** Finds KOTS Configs by locating files with:
+- `kind: Config`
+- `apiVersion: kots.io/*` (any version: v1beta1, v1beta2, v1, etc.)
 
-**Solution:** Only one embedded cluster config is allowed per project. Remove duplicate configs or move them to separate projects.
+**GVK filtering:** The linter distinguishes KOTS Config (`kots.io`) from Embedded Cluster Config (`embeddedcluster.replicated.com`) using Group-Version-Kind filtering. Both use `kind: Config` but belong to different API groups.
 
-**Problem:** Validation errors about Kubernetes version
+**Multiple configs error:** If multiple KOTS configs are found, each will show as failed with an actionable error message: "Remove duplicate configs or specify a single config file." Other linters continue running.
 
-**Solution:** Ensure the `spec.version` field uses a supported Kubernetes version. Check the embedded-cluster documentation for supported versions.
+**Example KOTS Config:**
+```yaml
+apiVersion: kots.io/v1beta1
+kind: Config
+metadata:
+  name: my-app-config
+spec:
+  groups:
+    - name: database
+      title: Database Settings
+      items:
+        - name: postgres_host
+          title: PostgreSQL Host
+          type: text
+          required: true
+          default: "postgres"
+```