fix: update ingressSecretMap even when secret is malformed

[akshaysngupta]

Checklist

• The title of the PR is clear and informative
• If applicable, the changes made in the PR have proper test coverage
• Issues addressed by the PR are mentioned in the description followed by Fixes.

Description

This PR fixes an issue in processing ingress event with TLS secret.
When ingress is processed, the referenced TLS secret is mapped to ingress and saved in a ingress-secret map.

In specific case where secret is malformed,, this step is skipped due to the continue statement. So later, when the certificate is fixed, it doesn't cause an event on AGIC and doesn't update the Application Gateway.
Secret is malformed in case customer is using a certificate manager which creates an empty secret initially and then fills the cert crt and key after generating them.

This is the place where secret handler checks if the secret is in the map or not.

application-gateway-kubernetes-ingress/pkg/k8scontext/secrets_handlers.go

Line 55 in 6bc8764

if h.context.ingressSecretsMap.ContainsValue(secKey) {

Fixes

Closes #893
Closes #728
Closes #763

[3quanfeng]

handle logging properly