Postee sending empty email for scanned image

Getting empty report via email for image scan.

### Received Email results:

### cfg.yaml
```
actions:
- type: email
name: my-email
user:
host: x.x.x.x
port: 25
sender: xxxx@xxx.com
recipients:
- xxxx
password:
enable: true
routes:
- name: email-route
input: contains(input.Metadata.OS.Family, "alpine")
#input: |
#contains(input.image,"alpine")
#input: input
actions:
- my-email
template: legacy
templates:
- name: slack-template
rego-package: postee.vuls.slack
- name: rego-html
rego-package: postee.vuls.html
- name: legacy
legacy-scan-renderer: html
- name: legacy-slack
legacy-scan-renderer: slack
- name: custom-email
url: null
- name: trivy-operator-jira
rego-package: postee.trivyoperator.jira
- name: trivy-operator-slack
rego-package: postee.trivyoperator.slack
templates:
- name: trivy-raw-json
rego-package: postee.rawmessage.json
name: tenant
AquaServer: https://xxxxxxxxxxx.com
```

### Trivy webhook run command:

`trivy webhook --url=http://postee-service.trivy-tools.svc.cluster.local:8084 -- image --format=json --ignore-unfixed --severity HIGH,CRITICAL,MEDIUM`

### Postee log:

### Trivy webhook run command result:

Start by reproducing the image scan with the Trivy webhook command and the cfg.yaml configuration, then trace how the legacy HTML template is rendered for the email action. Compare the generated report with the empty received email and use the Postee logs and webhook result shown in the issue to identify where content is lost. Done means image-scan emails contain the expected report.

Written by the indexing model from the issue text.