[BUG] Forecastle fails on empty TLS field in ingress

[MuneebAijaz]

Describe the bug It seems like forecastle panics on empty tls field in ingress

To Reproduce Create an Ingress with

  tls:
  - {} 

field, link it to a ForecastleApp CR. Forecastle pods will show panics. 2023/11/22 15:44:09 http: panic serving [::1]:38128: runtime error: index out of range [0] with length 0 Expected behavior There should be no panics, instead a nil/empty check

Screenshots If applicable, add screenshots to help explain your problem.

Environment

• Operator Version:
• Kubernetes/OpenShift Version: 4.13

Additional context Add any other context about the problem here.