feat(charts/capsule): added extra manifests in values file

[Llyth]

This will give the possibility to add extra kubernetes resources/objects such as Tenant, KEDA ScaledObject, configMaps.
Things that are not part of the chart itself but part of/related to Capsule.

[Llyth]

I've proceeded to the modifications that failed the previous run of GitHub actions workflows:

• the uppercase letter in extraManifests is removed in favor of "extra manifests" in the commit subject/PR title (https://github.com/projectcapsule/capsule/actions/runs/17646581576)
• line break at eof in extra-values.yaml (https://github.com/projectcapsule/capsule/actions/runs/17646581583)
• helm-docs regeneration (https://github.com/projectcapsule/capsule/actions/runs/17646581584/job/51466860033)

EDIT: added workflow runs links

[oliverbaehler]

Please run make helm-schema

[Llyth]

I've ran make helm-schema successfully.
Sorry for the delay and inconvenience.

[Llyth]

Installing chart with values file "charts/capsule/ci/extra-values.yaml"...

>>> helm install capsule-jpnz6c2ois charts/capsule --namespace capsule-system --wait --values charts/capsule/ci/extra-values.yaml --timeout 600s
I1006 10:03:51.006593   26391 warnings.go:110] "Warning: unknown field \"spec.defaultRegistry\""
Error: INSTALLATION FAILED: 1 error occurred:
	* Internal error occurred: failed calling webhook "tenants.projectcapsule.dev": failed to call webhook: Post "https://capsule-jpnz6c2ois-webhook-service.capsule-system.svc:443/tenants/mutating?timeout=30s": dial tcp 10.96.211.216:443: connect: connection refused

I've proceeded with modifications to the CI test with some random configMap instead and removed the example with a dummy Tenant to not confuse people and let them do as they wish (configMap, secret, other kubernetes object or crd).

In my case I do use it to add tenant, although it's not working in install because of webhook not being ready in time on default.
It is working if you set webhooks.hooks.tenants.enabled=false during your first install.

Reran the followings successfully:

• make helm-docs
• make helm-schema
• make helm-test

[oliverbaehler]

Whoops theres an error on main

[Llyth]

It's a common issue with webhook admission controllers, resource is created but not ready.
Any resource tied to webhooks will fail with either connection refused or timeout.

An example here with cert-manager whenever you try to add a cluster issuer with the install (issue: cert-manager/cert-manager#2908).

[oliverbaehler]

Yeah got that, talking about the warning :D