When kong chart is already deployed and in a broken state error is silently ignored because of name re-use

When user already has kong addon deployed in an existing cluster and it's in a broken state then no error will be displayed causing confusing test failures etc.

https://github.com/Kong/kubernetes-testing-framework/blob/b3ce22e2996d048ec4452d0369b36e1db094bca1/pkg/clusters/addons/kong/addon.go#L275-L277

There could be for instance more logic introduced around kong's helm release deployment or simply a warning being printed out whenever the problem described in this issue occurs.

### Acceptance criteria

- [ ] Log an error when chart is already deployed and there's an error deploying

Start in pkg/clusters/addons/kong/addon.go at the deployment logic around lines 275-277, and trace how an existing Kong Helm release error is handled. Make the described deployment failure visible through an error log, then verify the acceptance criterion against the broken, already-deployed chart scenario.

Written by the indexing model from the issue text.