[Mimecast] Fix template config and verify cursor test

[bhapas]

What does this PR do?

This PR fixes the template config in all data_streams in mimecast integration and also verifies assert.hit_count for cursor test.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

elastic-package stack down && elastic-package build && elastic-package stack up -d -v && eval "$(elastic-package stack shellinit)" && elastic-package test

Related issues

• Relates [mimecast] Issues with configuration #4921

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-02-23T15:39:23.291+0000

• Duration: 20 min 33 sec

Test stats 🧪

Test	Results
Failed	0
Passed	56
Skipped	0
Total	56

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (8/8)	💚
Files	100.0% (8/8)	💚
Classes	100.0% (8/8)	💚
Methods	95.726% (112/117)	👍 3.302
Lines	88.569% (1232/1391)	👎 -7.182
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[efd6]

LGTM

Note that there are duplication issues in the test data. I'm dealing with that in #5376, so I'll fix up the newly added events in that PR after this is merged.

[elasticmachine]

Package mimecast - 1.6.2 containing this change is available at https://epr.elastic.co/search?package=mimecast

[bn-jmynsberge]

I know this issue is closed, but I'm still seeing this error on 1.6.3:

error processing response: template: :1:16: executing "" at <.last_response.body.meta.pagination.next>: map has no entry for key "next"
error processing response: template: :1:27: executing "" at <.last_response.body.meta.pagination>: map has no entry for key "pagination"

It seems like this fix was only applied to the audit logs?